RE: g++: error: -fuse-linker-plugin is not supported in this configuration

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From: Jonathan Wakely
> On 23 April 2012 10:15, Hite, Christopher wrote:
> Do you mind answering the two questions below:
>
>> Two more dumb questions:
>> 1) Should I / how do I tell do it to build the standard libs with -flto?
>>
>> 2) Does it make sense to combine this with -ffunction-sections, -fdata-sections plus --gc-sections?  Or does LTO make that redundant?

> I wouldn't bother building the standard libs with LTO personally.  Do you have a reason to think you need to.  It's not done by default so obviously not essential.
I'm building one statically linked binary for deployment and I'm pretty sure a bunch of the standard libs is never used.  Things like "basic_ifstream<wchar_t..>"

I rebuilt boost with -flto and it make a bunch of weird warnings go away.  Maybe I should do the same with the standard libs.  On the other hand it doesn't do this automatically maybe there's a reason.

> Why don't you just keep it simple and try to get a GCC that works with LTO first?
It does now.  Seriously thanks!!!

> I'm suggesting unpacking the GMP, MPFR and MPC sources in the GCC source directory (renaming gmp-x.y.z to gmp, and mpfr-x.y.z to mpfr and mpc-x.y.z to mpc) and then building GCCC without any of --with-gmp etc.
I do use them to build binutils.


> Here's an earlier version of the page I keep suggesting you read, which doesn't use download_prerequisites:
> http://advogato.org/person/redi/diary/240.html
Thanks I wish I would have found this last week!


> It's not at all crazy.  The 'gcc' and 'g++' drivers just run other executables, including the cc1, cc1plus etc. executables to do preprocessing and compilation, the as executable to do assembling and the ld executable to do linking.  
> Looking for all of them in one place makes perfect sense, and since 'as' and 'ld' aren't part of GCC it makes sense to see if they're already installed in that same place as will be used for the other executables it depends on.
Yeah, I'd just expect you to look at the shell's path first.  That seems to be what other packages do when looking for a compiler, but I'm no expert.  Maybe there's some reason to check the path last.

Chris



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux