Re: [Gtk-osx-users] Failure while building gtk+
- From: John Ralls <jralls ceridwen us>
- To: GTK+-2 OSX Users <gtk-osx-users lists sourceforge net>
- Subject: Re: [Gtk-osx-users] Failure while building gtk+
- Date: Tue, 14 Sep 2010 13:50:56 -0700
On Sep 13, 2010, at 10:41 PM, John Ralls wrote:
>
> On Sep 13, 2010, at 9:52 PM, Phillip Heller wrote:
>
>> Greetings,
>>
>> I've successfully built the following once on my laptop, but I need to rebuild on my desktop:
>>
>> jhbuild bootstrap --ignore-system
>> jhbuild build meta-gtk-osx-bootstrap
>> jhbuild build meta-gtk-osx-core
>> jhbuild build meta-gtk-osx-python
>> jhbuild buildone librsvg
>>
>> I'm building under a separate user, which does not have my macports installation in it's path (same is true on the laptop). The .jhbuildrc-custom has the following customizations:
>>
>> _gtk_osx_use_jhbuild_python = True
>> append_autogenargs("python", "--with-universal-archs=32-bit --enable-universalsdk=/Developer/SDKs/MacOSX10.5.sdk")
>> branches["python"] = "http://www.python.org/ftp/python/2.6.4/Python-2.6.4.tar.bz2"
>>
>> setup_sdk(target="10.5", sdk_version="10.5", architectures=["i386"])
>>
>> os.environ["CC"] = "/usr/bin/gcc-4.0"
>>
>> build_policy = "updated-deps"
>>
>> Things seem to move along just fine, save the issue with Python's filesize and/or sum not matching, for which I must manually extract in a shell, and the issue with the Python Makefile ignoring the configure directives and having duplicate -arch and -sysroot definitions -- which is solved by hand editing the Makefile, and forcing the build phase.
>>
>> The issue I'm running into on the desktop is during the build of gtk+, I get hundreds and hundreds of errors similar to the following:
>>
>> In file included from /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:12,
>> from /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/Cocoa.framework/Headers/Cocoa.h:12,
>> from gtkstatusicon-quartz.c:26,
>> from gtkstatusicon.c:104:
>> /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:124: error: stray '@' in program
>> /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:124: error: syntax error before 'NSString'
>> /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:126: error: syntax error before '*' token
>> /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:127: error: syntax error before '*' token
>> /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:129: error: syntax error before '*' token
>> /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:130: error: syntax error before '*' token
>> /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:132: error: syntax error before '*' token
>> /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:132: error: syntax error before '*' token
>> /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:133: error: syntax error before '*' token
>> /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:133: error: syntax error before '*' token
>> /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:137: error: syntax error before '*' token
>> /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:138: error: syntax error before '*' token
>>
>> Both laptop and desktop are running 10.6.4 and have all applicable updates applied.
>>
>> The only discernable difference I can see is that the config.log for gtk+ on the desktop lacks --without-libjasper in the argument list supplied at configure time.
>>
>> I've manually configured with the addition of --without-libjasper, and I still get the errors.
>>
>> I'm thoroughly lost here.
>>
>
> Yes, it looks like the gtk-introspection patch is still screwed up. I'll have to work on it tomorrow.
The new patch is pushed and tested successfully on my machine.
There are two ways you can apply it: The easy way is to delete the source directory and re-run jhbuild build (if you've left that window at the error prompt from jhbuild, you can just select option 6). The somewhat more difficult way is to cd to to gtk+ source directory, reverse gtk-introspection.patch (you'll find it in ~/.cache/jhbuild), retrieve the new patch from github and apply it, then rebuild. If that doesn't make sense to you without more explanation, just do the delete-and-rebuild.
Regards,
John Ralls
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]