Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 121501 - dev-libs/liboil-0.3.7 failed to compile
Summary: dev-libs/liboil-0.3.7 failed to compile
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
: 121583 121585 121604 121640 121676 121690 121796 122108 122142 122171 122193 122217 122378 122443 122530 123090 123166 123382 123773 123805 123892 123903 123912 127045 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-02-03 21:16 UTC by patrick
Modified: 2006-03-21 01:02 UTC (History)
12 users (show)

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


Attachments
liboil build error (liboil_problem.log,197.07 KB, text/plain)
2006-02-08 03:48 UTC, Jared Greenwald
Details
ccHbjwsn.out reprocessed source stored into (ccHbjwsn.out,120.04 KB, text/plain)
2006-02-22 19:27 UTC, Lee
Details

Note You need to log in before you can comment on or make changes to this bug.
Description patrick 2006-02-03 21:16:08 UTC
liboil-0.3.7 failed to compile today with the command emerge -Duav world.
12 hours later I emerge synced again and the same error was returned.
CFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CXXFLAGS="${CFLAGS}"
MAKEOPTS="-j2"
Linux version 2.6.14-gentoo-r2 (root@frog) (gcc version 3.3.6 (Gentoo 3.3.6, ssp-3.3.6-1.0, pie-8.7.8)) #5 PREEMPT Sun Dec 4 12:44:55 PST 2005

composite_sse_2pix.c: In function `composite_in_argb_sse_2pix':
composite_sse_2pix.c:162: internal compiler error: in push_reload, at reload.c:1315
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugs.gentoo.org/> for instructions.
Preprocessed source stored into /var/tmp/portage/liboil-0.3.7/temp/ccG6WvGg.out file, please attach this to your bugreport.
make[3]: *** [libsse_la-composite_sse_2pix.lo] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Comment 1 Saleem Abdulrasool (RETIRED) gentoo-dev 2006-02-03 21:31:31 UTC
Can you please post the entire build log?
Comment 2 Mark Loeser (RETIRED) gentoo-dev 2006-02-03 21:54:55 UTC
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 :)
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2006-02-04 12:33:16 UTC
*** Bug 121583 has been marked as a duplicate of this bug. ***
Comment 4 patrick 2006-02-04 12:47:56 UTC
I re-emerged gcc and everything worked out fine...
the output log no longer exists.
Comment 5 Jakub Moc (RETIRED) gentoo-dev 2006-02-04 12:59:41 UTC
*** Bug 121585 has been marked as a duplicate of this bug. ***
Comment 6 Jakub Moc (RETIRED) gentoo-dev 2006-02-04 15:57:15 UTC
*** Bug 121604 has been marked as a duplicate of this bug. ***
Comment 7 Robert Golding 2006-02-04 16:27:51 UTC
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.
Comment 8 Mark Loeser (RETIRED) gentoo-dev 2006-02-04 17:09:17 UTC
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.
Comment 9 Jakub Moc (RETIRED) gentoo-dev 2006-02-05 02:34:15 UTC
*** Bug 121640 has been marked as a duplicate of this bug. ***
Comment 10 Markus Goppelt 2006-02-05 03:13:13 UTC
# 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".
Comment 11 Jakub Moc (RETIRED) gentoo-dev 2006-02-05 03:21:10 UTC
(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

Comment 12 Jakub Moc (RETIRED) gentoo-dev 2006-02-05 09:07:23 UTC
*** Bug 121676 has been marked as a duplicate of this bug. ***
Comment 13 Jakub Moc (RETIRED) gentoo-dev 2006-02-06 00:56:06 UTC
*** Bug 121690 has been marked as a duplicate of this bug. ***
Comment 14 Jakub Moc (RETIRED) gentoo-dev 2006-02-06 02:17:07 UTC
*** Bug 121796 has been marked as a duplicate of this bug. ***
Comment 15 Robert Golding 2006-02-07 01:08:50 UTC
(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 :-)
Comment 16 Jürgen Habig 2006-02-07 12:34:18 UTC
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
Comment 17 Jared Greenwald 2006-02-08 03:48:36 UTC
Created attachment 79215 [details]
liboil build error

emerge info && emerge liboil
Comment 18 Jared Greenwald 2006-02-08 03:50:02 UTC
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.
Comment 19 Jakub Moc (RETIRED) gentoo-dev 2006-02-08 04:26:30 UTC
*** Bug 122108 has been marked as a duplicate of this bug. ***
Comment 20 Jakub Moc (RETIRED) gentoo-dev 2006-02-08 08:57:45 UTC
(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*. 

Comment 21 Jakub Moc (RETIRED) gentoo-dev 2006-02-08 09:08:13 UTC
*** Bug 122142 has been marked as a duplicate of this bug. ***
Comment 22 Jared Greenwald 2006-02-08 09:37:45 UTC
(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.
Comment 23 Jakub Moc (RETIRED) gentoo-dev 2006-02-08 13:37:20 UTC
*** Bug 122171 has been marked as a duplicate of this bug. ***
Comment 24 Carsten Lohrke (RETIRED) gentoo-dev 2006-02-08 19:30:25 UTC
*** Bug 122193 has been marked as a duplicate of this bug. ***
Comment 25 Jakub Moc (RETIRED) gentoo-dev 2006-02-09 01:24:48 UTC
*** Bug 122217 has been marked as a duplicate of this bug. ***
Comment 26 Jakub Moc (RETIRED) gentoo-dev 2006-02-10 08:22:38 UTC
*** Bug 122378 has been marked as a duplicate of this bug. ***
Comment 27 Jakub Moc (RETIRED) gentoo-dev 2006-02-11 03:28:02 UTC
*** Bug 122443 has been marked as a duplicate of this bug. ***
Comment 28 Jakub Moc (RETIRED) gentoo-dev 2006-02-12 02:08:58 UTC
*** Bug 122530 has been marked as a duplicate of this bug. ***
Comment 29 Harald van Dijk (RETIRED) gentoo-dev 2006-02-12 02:31:30 UTC
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.
Comment 30 Jakub Moc (RETIRED) gentoo-dev 2006-02-16 14:25:25 UTC
*** Bug 123090 has been marked as a duplicate of this bug. ***
Comment 31 Jakub Moc (RETIRED) gentoo-dev 2006-02-17 06:58:51 UTC
*** Bug 123166 has been marked as a duplicate of this bug. ***
Comment 32 Jakub Moc (RETIRED) gentoo-dev 2006-02-19 06:58:11 UTC
*** Bug 123382 has been marked as a duplicate of this bug. ***
Comment 33 Jakub Moc (RETIRED) gentoo-dev 2006-02-22 18:37:08 UTC
*** Bug 123773 has been marked as a duplicate of this bug. ***
Comment 34 Lee 2006-02-22 19:27:23 UTC
Created attachment 80493 [details]
ccHbjwsn.out reprocessed source stored into
Comment 35 Carsten Lohrke (RETIRED) gentoo-dev 2006-02-23 07:51:02 UTC
*** Bug 123805 has been marked as a duplicate of this bug. ***
Comment 36 Jakub Moc (RETIRED) gentoo-dev 2006-02-24 01:54:32 UTC
*** Bug 123892 has been marked as a duplicate of this bug. ***
Comment 37 Jakub Moc (RETIRED) gentoo-dev 2006-02-24 01:59:35 UTC
*** Bug 123903 has been marked as a duplicate of this bug. ***
Comment 38 Carsten Lohrke (RETIRED) gentoo-dev 2006-02-24 03:47:34 UTC
*** Bug 123912 has been marked as a duplicate of this bug. ***
Comment 39 Jakub Moc (RETIRED) gentoo-dev 2006-03-21 01:02:56 UTC
*** Bug 127045 has been marked as a duplicate of this bug. ***