Summary: | gnome-base/nautilus-2.22.5.1 does not compile due to missing includes | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Petri Hintukainen <phi> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | mike, mycroes, phi, qian.qiao |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 238694, 254034 | ||
Attachments: |
Add #include <sys/stat.h>
Updated Ebuild to remove LDFLAGS build.log |
Description
Petri Hintukainen
2008-08-04 08:41:20 UTC
Created attachment 162173 [details, diff]
Add #include <sys/stat.h>
Proposed fix
I'm seeing the exact same issue here. gcc-4.3.1-r1 glibc-2.7-r2 I can also confirm that the proposed patch by Petri fixes the issue. Patch doesn't work for me on x86 with gcc-4.3.1, glibc-2.8_p20080602-r0 error: with patch: rm -fr .libs/libnautilus-private.lax creating libnautilus-private.la (cd .libs && rm -f libnautilus-private.la && ln -s ../libnautilus-private.la libnautilus-private.la) make[2]: Leaving directory `/var/tmp/portage/gnome-base/nautilus-2.22.5.1-r2/work/nautilus-2.22.5.1/libnautilus-private' Making all in src make[2]: Entering directory `/var/tmp/portage/gnome-base/nautilus-2.22.5.1-r2/work/nautilus-2.22.5.1/src' /usr/bin/orbit-idl-2 -I /usr/share/idl/bonobo-activation-2.0 -I /usr/share/idl/bonobo-2.0 -I.. nautilus-shell-interface.idl orbit-idl-2 2.14.13 compiling mode, hide preprocessor errors, passes: stubs skels common headers Processing file nautilus-shell-interface.idl Error: Empty file ** (orbit-idl-2:3007): WARNING **: nautilus-shell-interface.idl compilation failed make[2]: *** [nautilus_shell_interface_idl_stamp] Error 1 make[2]: Leaving directory `/var/tmp/portage/gnome-base/nautilus-2.22.5.1-r2/work/nautilus-2.22.5.1/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/gnome-base/nautilus-2.22.5.1-r2/work/nautilus-2.22.5.1' make: *** [all] Error 2 Same error without the patch, thus i feel that glibc version is not the issue here. @Petri can you try and rebuild with "safer" LDFLAGS @Qian emerge --info would be nice to compare Removing some Wonky flags during compile fixed it for me without includes. I'll attach an updated ebuild, Can you Test and confirm if it works @Petri and @Quian? Created attachment 162278 [details]
Updated Ebuild to remove LDFLAGS
Added some removal of flags.
(In reply to comment #5) > Created an attachment (id=162278) [edit] > Updated Ebuild to remove LDFLAGS > > Added some removal of flags. > No way are we going to filter flags like this. To all of you, please try with sane CFLAGS and the default LDFLAGS for your profile. If that works, then reinsert one by one your {C,LD}FLAGS to see which one breaks. Thanks I was running into the same issue, was hoping it would've gotten fixed by now... In response to #6: I have no custom LDFLAGS set, I've already changed and even stripped my CFLAGS with the exception of -pipe and was still running into the same issue. I'm using gcc-4.1.2, glibc-2.6.1 on a system using the 2008.0 amd64 default profile and I use paludis as package manager. If more information is required, please say so. (In reply to comment #7) > I was running into the same issue, was hoping it would've gotten fixed by > now... Which issue? The #includes one? Have you tried the patch? Thanks (In reply to comment #6) > please try with > sane CFLAGS and the default LDFLAGS for your profile. If that works, then > reinsert one by one your {C,LD}FLAGS to see which one breaks. Didn't help (I removed all CFLAGS and LDFLAGS from Make.conf). BTW, I have exactly same problem with gnome-screensaver-2.22.2. Maybe the problem is related to some other gnome headers (older version of some header might have #included <sys/stat.h> ?). (In reply to comment #8) > (In reply to comment #7) > > I was running into the same issue, was hoping it would've gotten fixed by > > now... > > Which issue? The #includes one? Have you tried the patch? The issue where it won't compile and fail on the exact same error. I haven't tried the patch yet, I'm trying to wait for someone else to figure out what's going on but thought it might be helpful I let you know that LDFLAGS and CFLAGS don't seem to affect this issue... Could anyone with this bug provide : 1) a simple "emerge --info" (the one provided by Petri is obviously "emerge --info --verbose"), 2) a *full* build.log as portage strongly suggests, 3) the output of "emerge -pv nautilus" Thank you. And FYI, on a rather standard ~amd64, I cannot reproduce this bug, so please send us useful logs so that we can try to identify the breakage. Created attachment 162349 [details]
build.log
More details as requested: gcc-4.3.1-r1 glibc-2.7-r2 # paludis --info nautilus can be found here: http://misc.ajiaojr.net/~ajiaojr/nautilus-info.log build log can be found here: http://misc.ajiaojr.net/~ajiaojr/nautilus.log # paludis -ip1 nautilus Building target list... Building dependency list... These packages will be installed: * gnome-base/nautilus [U 2.22.4 -> 2.22.5.1-r1] <target> X -beagle -debug gnome -tracker Total: 1 package (1 upgrade) > 3) the output of "emerge -pv nautilus"
WARNING: repository at /usr/local/portage is missing a repo_name entry
WARNING: repository at /usr/portage/local/oma is missing a repo_name entry
These are the packages that would be merged, in order:
Calculating dependencies
... done!
[ebuild R ] gnome-base/nautilus-2.22.5.1 USE="X gnome -beagle -debug" 0 kB [?=>0]
Total: 1 package (1 reinstall), Size of downloads: 0 kB
Portage tree and overlays:
[0] /usr/portage
[?] indicates that the source repository could not be determined
(Missing repository was my own overlay with gnome-base/nautilus-2.22.5.1 + the patch)
@remi for Comment#6 x86 Default 2008.0 Profile, ${CHOST}="i686-pc-linux-gnu" glibc-2.6.1-r0 Results from ${CLFAGS}="-O2 -pipe", ${LDFLAGS}="-W1,-O1" GCC-4.1.2 = builds fine, without patch GCC-4.2.4 = builds fine, without patch GCC-4.3.1 = builds fine, without patch glibc-2.6.1-r0 Results from ${CLFAGS}="-O2 -pipe", ${LDFLAGS}="-W1,-O1,--as-needed" GCC-4.1.2 = builds fine, without patch GCC-4.2.4 = builds fine, without patch GCC-4.3.1 = builds fine, without patch glibc-2.6.1-r0 Results from ${CLFAGS}="-O2 -pipe", ${LDFLAGS}="-W1,-O1,--enable-new-dtags" GCC-4.1.2 = builds fine, without patch GCC-4.2.4 = builds fine, without patch GCC-4.3.1 = builds fine, without patch glibc-2.8_p20080602-r0 results from ${CLFAGS}="-O2 -march=core2 -pipe -fomit-frame-pointer -g -ggdb", ${LDFLAGS}="-W1,-O1" GCC-4.3.1 = builds fine, without patch GCC-4.3.1 = builds fine, with patch Please let me know if you need more information regarding tests, i tried to cover as many bases as i could with my hardware/software setup. -Mike (In reply to comment #13) > More details as requested: > > gcc-4.3.1-r1 > glibc-2.7-r2 > > # paludis --info nautilus can be found here: > http://misc.ajiaojr.net/~ajiaojr/nautilus-info.log > > build log can be found here: > http://misc.ajiaojr.net/~ajiaojr/nautilus.log > > # paludis -ip1 nautilus > Building target list... > Building dependency list... > > These packages will be installed: > > * gnome-base/nautilus [U 2.22.4 -> 2.22.5.1-r1] <target> > X -beagle -debug gnome -tracker > > Total: 1 package (1 upgrade) > I've then tried with the following combinations, all done with gcc-4.3.1-r1 and glibc-2.7-r2 CFLAGS= LDFLAGS=-Wl,-O1 fail with the same error CFLAGS=-O1 LDFLAGS=-Wl,-O1 fail with the same error CFLAGS=-O2 LDFLAGS=-Wl,-O1 fail with the same error CFLAGS=-O2 -pipe LDFLAGS=-Wl,-O1 fail with the same error CFLAGS=-O2 -pipe -march=core2 LDFLAGS=-Wl,-O1 fail with the same error Downgrading dev-libs/glib from 2.17.6 to 2.16.5 solved the problem. ( emerge --oneshot =dev-libs/glib-2.16.5 libbonobo gnome-vfs libgnome libbonoboui libgnomeui gnome-desktop nautilus ) It seems nautilus-2.22.5.1 does not compile with glib-2.17.6, running emerge --oneshot =dev-libs/glib-2.17.6 nautilus fails again. glib-2.17.6 is from gnome overlay, so sorry for the trouble... problems that occurs when mix and matching stable versions with overlay versions is up to the users, sorry there's nothing to fix here, if you can reproduce the bug with nautilus 2.23, feel free to reopen this bug. The issue at hand is that someone in the gnome overlay is keywording stuff as x86/amd64. I noticed it for some other package, but I don't use the gnome overlay for anything at all... I'm removing the overlay, seems everything is working again now (except for stuff I had to recompile). well that's stupid to keyword things stable in a _dev_ overlay indeed, hope the guy concerned will see this and won't do it again (I do hope it's an error of manipulation). libbonoboui was indeed marked as stable for amd64 and ppc in the overlay. Fixed for good :) Thanks (In reply to comment #21) > libbonoboui was indeed marked as stable for amd64 and ppc in the overlay. > > Fixed for good :) > > Thanks > As was glib... And I doubt it was just libbonobo and glib, could be more... (In reply to comment #22) > As was glib... And I doubt it was just libbonobo and glib, could be more... Nope, I've rechecked the whole overlay and it's 100% ~ only. Only libbonobo was affected. You might want to check other overlays (if you have any) or files in /etc/portage such as package.unmask or package.keywords. Thanks (In reply to comment #23) > You might want to check other overlays (if you have any) or files in > /etc/portage such as package.unmask or package.keywords. I was wrong indeed, had glib ~amd64 in keywords.conf which caused it to accept the gnome overlay glib... Reopening And this is now actually fixed in portage. Adding to breakage meta. Thanks |