Summary: | dev-libs/liboil-0.3.7 failed to compile | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | patrick <patroy1> |
Component: | [OLD] Library | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | akos, curtlee2002, halcy0n, hernan, juho.vuori, michael, penberg, raymond, truedfx, waffel, wingenroth, zarick |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
liboil build error
ccHbjwsn.out reprocessed source stored into |
Description
patrick
2006-02-03 21:16:08 UTC
Can you please post the entire build log? Please update to gcc-3.4.4. If it is still a problem, reopen the bug and attach the preprocessed output to the bug like the error told you :) *** Bug 121583 has been marked as a duplicate of this bug. *** I re-emerged gcc and everything worked out fine... the output log no longer exists. *** Bug 121585 has been marked as a duplicate of this bug. *** *** Bug 121604 has been marked as a duplicate of this bug. *** Why is this still "RESOLVED INVALID" when people are obviously starting to have real problems with the latest --sync version of 0.3.7 compiling. Am I allowed to reopen the bug? My emerge --info, compile error message and preprocessed source are at #121583. I do not consider a forced upgrade to gcc-3.4.4 a satisfactory fix. gcc-3.4.4 is the current stable version of gcc. Bugs in 3.3 will not be fixed since we can't support something upstream does not support. *** Bug 121640 has been marked as a duplicate of this bug. *** # emerge --search gcc ...snip... * sys-devel/gcc Latest version available: 3.4.5 Latest version installed: 3.4.5 Size of files: 28,499 kB Homepage: http://www.gnu.org/software/gcc/gcc.html Description: The GNU Compiler Collection. Includes C/C++, java compilers, pie+ssp extensions, Haj Ten Brugge runtime bounds checking License: GPL-2 LGPL-2.1 # emerge --info Portage 2.1_pre4-r1 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.6-r2, 2.6.12-gentoo-r6 i686) ================================================================= System uname: 2.6.12-gentoo-r6 i686 Intel(R) Pentium(R) M processor 1.86GHz Gentoo Base System version 1.12.0_pre15 ...snip... Why does "emerge --info" say gcc-3.3.6? I have version 3.4.5! Do I have to downgrade to 3.4.4 in order to emerge liboil-0.3.7? I'm using the "~x86" keyword because of my "ati-drivers". (In reply to comment #10) > Why does "emerge --info" say gcc-3.3.6? I have version 3.4.5! > Do I have to downgrade to 3.4.4 in order to emerge liboil-0.3.7? I'm using the > "~x86" keyword because of my "ati-drivers". http://www.gentoo.org/doc/en/gcc-upgrading.xml *** Bug 121676 has been marked as a duplicate of this bug. *** *** Bug 121690 has been marked as a duplicate of this bug. *** *** Bug 121796 has been marked as a duplicate of this bug. *** (In reply to comment #8) > gcc-3.4.4 is the current stable version of gcc. Bugs in 3.3 will not be fixed > since we can't support something upstream does not support. > My question would be - "Is it a bug in the old gcc, or a bug in how the new liboil has been written, so that it will not work with an earlier, but still current, version of gcc?" Anyhoo, I have upgraded, my E-17 hates it :-( , but now liboil compiles, yay :-) Hello together, i upgraded to gcc 3.4.5 and it works. fine thanks to all I think it is only a problem with the old gcc greetings J. Habig Created attachment 79215 [details]
liboil build error
emerge info && emerge liboil
I'm still seeing the problem even after having upgraded to gcc-3.4.4. I followed the guide's emerge -e method, but only got about halfway through emerge -e world since it fails on liboil still. See the attachment for my build error. *** Bug 122108 has been marked as a duplicate of this bug. *** (In reply to comment #18) > I'm still seeing the problem even after having upgraded to gcc-3.4.4. I > followed the guide's emerge -e method, but only got about halfway through > emerge -e world since it fails on liboil still. See the attachment for my > build error. Competely different issue, file a new bug, this bug is about 3.3.x ICE *only*. *** Bug 122142 has been marked as a duplicate of this bug. *** (In reply to comment #20) > (In reply to comment #18) > > I'm still seeing the problem even after having upgraded to gcc-3.4.4. I > > followed the guide's emerge -e method, but only got about halfway through > > emerge -e world since it fails on liboil still. See the attachment for my > > build error. > > Competely different issue, file a new bug, this bug is about 3.3.x ICE *only*. > Actually, it was recently pointed out to me that my CFLAGS (noted above in the attachment) were wrong. I fixed them and now everything seems cool. *** Bug 122171 has been marked as a duplicate of this bug. *** *** Bug 122193 has been marked as a duplicate of this bug. *** *** Bug 122217 has been marked as a duplicate of this bug. *** *** Bug 122378 has been marked as a duplicate of this bug. *** *** Bug 122443 has been marked as a duplicate of this bug. *** *** Bug 122530 has been marked as a duplicate of this bug. *** Considering the number of dupes, maybe it would be a good idea to have the liboil ebuild work around this, even if gcc can't be fixed? gcc 3.3* with -O3 seems to work -- it's just with -O[12] that I can see this error on my machine -- so it would be easy enough to force that to all 3.3* users. Alternatively, a clear error message saying this is a known issue that won't be fixed, and telling users to upgrade their gcc, would also work. *** Bug 123090 has been marked as a duplicate of this bug. *** *** Bug 123166 has been marked as a duplicate of this bug. *** *** Bug 123382 has been marked as a duplicate of this bug. *** *** Bug 123773 has been marked as a duplicate of this bug. *** Created attachment 80493 [details]
ccHbjwsn.out reprocessed source stored into
*** Bug 123805 has been marked as a duplicate of this bug. *** *** Bug 123892 has been marked as a duplicate of this bug. *** *** Bug 123903 has been marked as a duplicate of this bug. *** *** Bug 123912 has been marked as a duplicate of this bug. *** *** Bug 127045 has been marked as a duplicate of this bug. *** |