Gentoo Archives: gentoo-alt

From: Junqi Hu <junqihu@××.com>
To: gentoo-alt@l.g.o
Subject: Re: [gentoo-alt] Problem with dev-python/pygtk in Mac OS X 10.8
Date: Tue, 18 Sep 2012 12:05:30
Message-Id: 8CD512F3-45E4-4B2D-8B2F-985BCC8E428A@me.com
In Reply to: Re: [gentoo-alt] Problem with dev-python/pygtk in Mac OS X 10.8 by Konstantin Tokarev
1 On 2012-9-18, at 下午4:59, Konstantin Tokarev <annulen@××××××.ru> wrote:
2
3 >
4 > 18.09.2012, 09:15, "Junqi Hu" <junqihu@××.com>:
5 >> On 2012-8-30, at 下午8:21, Konstantin Tokarev <annulen@××××××.ru> wrote:
6 >>
7 >>> 30.08.2012, 12:12, "Junqi Hu" <junqihu@××.com>:
8 >>>> Hi, all.
9 >>>>
10 >>>> The compiling procedure of dev-python/pygtk is broken when I install elogviewer by gentoo-prefix.
11 >>>> I attache the build.log of this ebuild.
12 >>>>
13 >>>> Any hint?
14 >>>
15 >>>> /System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:409: error: stray '@' in program
16 >>>
17 >>> Seems like your GTK pulls in NSObjCRuntime.h into pure C code. It should either be compiled as Objective C,
18 >>> or you should rebuild GTK for X11 instead of aqua.
19 >>>
20 >>> --
21 >>> Regards,
22 >>> Konstantin
23 >>
24 >> thank you.
25 >> I have changed the USE in make.conf as follows:
26 >> USE="X -aqua cjk emacs gtk -minimal nls -kde -qt -qt4 unicode"
27 >> in order to build applications with X11.
28 >> Now, elogviewer has been emerged successfully. However, there is some bug when running elogviewer:
29 >> $ elogviewer
30 >> /Users/junqihu/Gentoo/usr/lib/python2.7/site-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
31 >> warnings.warn(str(e), _gtk.Warning)
32 >> Traceback (most recent call last):
33 >> File "/Users/junqihu/Gentoo/usr/bin/elogviewer", line 596, in <module>
34 >> main(sys.argv[1:])
35 >> File "/Users/junqihu/Gentoo/usr/bin/elogviewer", line 584, in main
36 >> os.chdir("/var/log/portage")
37 >> OSError: [Errno 2] No such file or directory: '/var/log/portage'
38 >>
39 >> It is obvious that the ebuild of elogviewer should be modified
40 >
41 > Seems like it has hardcoded '/var/log/portage' path, so it needs to be patched.
42 >
43 > I'd recommended you to use elogv instead, it works fine for me.
44 >
45 > --
46 > Regards,
47 > Konstantin
48 >
49
50
51 Thanks.
52
53 That's great, except its interface.
54
55 ---
56 Best regards,
57
58 Junqi Hu
59 junqihu@××.com