Re: [Gtk-osx-users] Build glib

[John Ralls <jralls ceridwen fremont ca us>]

On Nov 22, 2010, at 12:39 PM, Gertwin Groen wrote:

> I wanted an 64 bit version so I removed the 32 bit version first
> before compiling 64 bit.
> 
> I am using the standard compiler.
> bash-3.2$ cc -v
> Using built-in specs.
> Target: i686-apple-darwin10
> Configured with: /var/tmp/gcc/gcc-5664~105/src/configure
> --disable-checking --enable-werror --prefix=/usr --mandir=/share/man
> --enable-languages=c,objc,c++,obj-c++
> --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/
> --with-slibdir=/usr/lib --build=i686-apple-darwin10
> --program-prefix=i686-apple-darwin10- --host=x86_64-apple-darwin10
> --target=i686-apple-darwin10 --with-gxx-include-dir=/include/c++/4.2.1
> Thread model: posix
> gcc version 4.2.1 (Apple Inc. build 5664)
> 
> Strange is that the jhbuild bootstrap and jhbuild build
> meta-gtk-osx-bootstrap wen well.
> 
> Regards,
> Gertwin
> 
> 
> 
> 2010/11/22 John Ralls <jralls ceridwen fremont ca us>:
>> 
>> On Nov 21, 2010, at 2:08 PM, Gertwin Groen wrote:
>> 
>>> Few days ago I build gtk-osx for i386 which went well.
>>> Today I want to build it for x64.
>>> 
>>> Everything went well until glib:
>>> 
>>> *** Configuring glib *** [2/11]
>>> ...
>>> 
>>> configure: WARNING: No ANSI prototypes found in library. (-std1 didn't work.)
>>> ...
>>> 
>>> checking size of char... 0
>>> checking size of short... 0
>>> checking size of long... 0
>>> checking size of int... 0
>>> checking size of void *... 0
>>> checking size of long long... 0
>>> checking size of __int64... 0
>>> configure: error:
>>> *** GLib requires a 64 bit type. You might want to consider
>>> *** using the GNU C compiler.
>>> 
>>> After this error I tried to rebuild my i386 build, which generates the
>>> same errors.
>>> 
>>> Yesterday I upgraded to 10.6.5, I doubt this is the cause.
>>> Does anyone know what is the cause of this problem and how to solve it?
>>> 
>> 
>> Not really enough information. Are you building in separate prefixes and checkoutroots? (You should be.)
>> 
>> The "consider using the GNU C compiler" message is interesting. You didn't set $CC to llvm or clang, did you?
>> 


Like I said, not enough information. 

I've done 6 builds in the last 3 days with no problems, including a git-master build, so it isn't a gtk-osx change that's messing you up. (The last change to the modulesets was November 5, and it was a trivial change because github only accepts https connections. Nothing at all to do with glib.)

My best guess is that you changed something in .jhbuildrc-custom when you switched to x86_64 so that whatever that configure test is fails. You'll have to either look at your changes there or dig into glib's configure and config.log to find exactly what's wrong.

Regards,
John Ralls