Re: [lto] LDFLAGS get lost in stage2

On Tue, May 19, 2009 at 11:18, Joseph S. Myers wrote: > On Tue, 19 May 2009, Eric Fisher wrote: > >> Hello, >> >> I have the libelf installed in a non-standard path, so when I build >> the lto branch, I set the such env variables, >> >> $ export CPPFLAGS="-I"  <- Only needed if >> libelf is in a n

Re: [lto] LDFLAGS get lost in stage2

On Tue, 19 May 2009, Eric Fisher wrote: > Hello, > > I have the libelf installed in a non-standard path, so when I build > the lto branch, I set the such env variables, > > $ export CPPFLAGS="-I" <- Only needed if > libelf is in a non-standard path > $ export LDFLAGS="-L" <- Only needed i

Re: [lto] LDFLAGS get lost in stage2

On Tue, May 19, 2009 at 02:29, Eric Fisher wrote: > I look into the Makefile and find that LDFLAGS is set as BOOT_LDFLAGS > scine stage2, so I have to set this variable also. > > Is it a right way that it should go? Yes, thanks for catching this. I will update the wiki. Diego.

[lto] LDFLAGS get lost in stage2

Hello, I have the libelf installed in a non-standard path, so when I build the lto branch, I set the such env variables, $ export CPPFLAGS="-I" <- Only needed if libelf is in a non-standard path $ export LDFLAGS="-L" <- Only needed if libelf is in a non-standard path But, lto-plugin is fa