Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 490638 - dev-libs/glib-2.36.4-r1: gentoo_prefix failed (compile phase)
Summary: dev-libs/glib-2.36.4-r1: gentoo_prefix failed (compile phase)
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo/Alt
Classification: Unclassified
Component: Mac OSX (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Prefix
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-07 01:46 UTC by yegle
Modified: 2014-02-11 20:29 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log for glib-2.36.4-r1 (build_log_glib_2.36.4_r1.txt,504.70 KB, text/plain)
2013-11-07 01:54 UTC, yegle
Details
emerge --info (emerge_info.txt,14.75 KB, text/plain)
2013-11-07 01:55 UTC, yegle
Details
build.log for python-2.7.5-r4 (build_log_python_2.7.5_r4.zip,67.12 KB, application/octet-stream)
2013-11-07 01:56 UTC, yegle
Details

Note You need to log in before you can comment on or make changes to this bug.
Description yegle 2013-11-07 01:46:13 UTC
In file included from /System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:161,
                 from /Users/yegle/.gentoo/var/tmp/portage/dev-libs/glib-2.36.4-r1/work/glib-2.36.4/gio/gnextstepsettingsbackend.c:28:
/System/Library/Frameworks/Foundation.framework/Headers/NSUserNotification.h:16: error: expected ',' or '}' before '__attribute__'


The exact error message shows when compiling python-2.7.5-r4


build.log http://bpaste.net/show/147460/
emerge --info http://bpaste.net/show/147461/

build.log for python-2.7.5-r4 http://bpaste.net/show/147462/

Reproducible: Always
Comment 1 Chí-Thanh Christopher Nguyễn gentoo-dev 2013-11-07 01:51:12 UTC
Please do not use pastebins in bugzilla, as they tend to expire. Use attachments instead.
Comment 2 yegle 2013-11-07 01:54:26 UTC
Created attachment 362716 [details]
build.log for glib-2.36.4-r1
Comment 3 yegle 2013-11-07 01:55:34 UTC
Created attachment 362718 [details]
emerge --info
Comment 4 yegle 2013-11-07 01:56:55 UTC
Created attachment 362720 [details]
build.log for python-2.7.5-r4
Comment 5 Fabian Groffen gentoo-dev 2013-11-10 10:43:06 UTC
which OSX is this, and can you show me the relevant line from Foundation.h, e.g.

sed -n '161p' /System/Library/Frameworks/Foundation.framework/Headers/Foundation.h
Comment 6 yegle 2013-11-10 16:14:50 UTC
(In reply to Fabian Groffen from comment #5)
> which OSX is this, and can you show me the relevant line from Foundation.h,
> e.g.
> 
> sed -n '161p'
> /System/Library/Frameworks/Foundation.framework/Headers/Foundation.h

@Fabian,

It's OSX Mavericks.

sed -n '161p' /System/Library/Frameworks/Foundation.framework/Headers/Foundation.h
#import <Foundation/NSUserNotification.h>
Comment 7 yegle 2013-11-12 05:46:16 UTC
The problem still exists after upgrading to XCode 5.0.2.

After setting CC to clang and CXX to clang++ (the one comes with xcode), it passes the compile phase without a problem.
Comment 8 Fabian Groffen gentoo-dev 2013-11-12 06:43:06 UTC
hmmmm, weird.  It appears line 16 is the problem (I mistakenly wrote 161), I suspect a type or something that isn't known to gcc for some reason.
Comment 9 yegle 2013-11-12 06:45:02 UTC
@Fabian

$ sed -n '16p' /System/Library/Frameworks/Foundation.framework/Headers/NSUserNotification.h
    NSUserNotificationActivationTypeReplied NS_AVAILABLE(10_9, NA) = 3

Hope this helps.
Comment 10 Fabian Groffen gentoo-dev 2013-12-17 21:02:34 UTC
what is your compiler?  gcc-config -l?
Comment 11 Fabian Groffen gentoo-dev 2014-02-11 20:27:15 UTC
Your CHOST is darwin12, so you likely upgraded your Mac and didn't re-bootstrap.  We can't support that, really, although rebuilding your gcc *might* help.  No guarantees though.
Comment 12 yegle 2014-02-11 20:29:50 UTC
(In reply to Fabian Groffen from comment #11)
> Your CHOST is darwin12, so you likely upgraded your Mac and didn't
> re-bootstrap.  We can't support that, really, although rebuilding your gcc
> *might* help.  No guarantees though.

Ah thank you for pointing out this. I'll re-bootstrap and see if it fixes this problem.