Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 241596 - build crash sci-libs/cln-1.2.2 with a certain LTCFLAGS
Summary: build crash sci-libs/cln-1.2.2 with a certain LTCFLAGS
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: x86 Linux
: High minor (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-12 13:15 UTC by pavel
Modified: 2008-10-13 15:39 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pavel 2008-10-12 13:15:53 UTC
sci-libs/cln-1.2.2 is failed to build (linking stage) with somewhat extreme LTCFLAGS settings:
LTCFLAGS="-O2 -march=core2 -finline-functions -pipe -funroll-loops -momit-leaf-frame-pointer"

However, successful merge with
LTCFLAGS="-O2 -march=core2"

P.S. I didn't dig into where ld actually got stuck in.

Reproducible: Always
Comment 1 Wormo (RETIRED) gentoo-dev 2008-10-13 02:09:09 UTC
How did you change the LTCFLAGS value, did you just update CFLAGS in your /etc/make.conf or did you have to recompile libtool with the less aggressive CFLAGS?
Comment 2 pavel 2008-10-13 06:32:46 UTC
(In reply to comment #1)
> How did you change the LTCFLAGS value, did you just update CFLAGS in your
> /etc/make.conf or did you have to recompile libtool with the less aggressive
> CFLAGS?
> 

libtool recompile

... and I cannot reproduce error anymore, can speculate only: libtool was built with gcc 4.3.1, it's 4.3.2 now. Having libtool (4.3.1), LTCFLAGS as before and new gcc 4.3.2 may cause this trouble.

Now it's ok even with LTCFLAGS="-O2 -march=core2 -finline-functions -pipe -funroll-loops -momit-leaf-frame-pointer"
Comment 3 Wormo (RETIRED) gentoo-dev 2008-10-13 06:34:18 UTC
Is it ok to close this bug then?
Comment 4 pavel 2008-10-13 06:54:10 UTC
(In reply to comment #3)
> Is it ok to close this bug then?
> 

I guess so.