Re: g++: error: -fuse-linker-plugin is not supported in this configuration
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
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. Why don't you just keep it simple and try to get a GCC that works with LTO first? > From: Jonathan Wakely >> Did you click on the link and read it? The second "easy way" doesn't need you to be root. > The second "easy way" doesn't work for me either. My dev box doesn't have access to the internet. Sometimes I have to ask other people to download stuff for me or encrypt things as mail attachements. > "Commerzbank we hate technology; we wish it would just go away!" OK, but if you bothered to look at the download_prerequisities script you'll see it's downloading the support library sources and putting them in the GCC source directory. Since you have already downloaded the files yourself, you could just put them in the GCC dir yourself. >> Do you actually need those libraries installed for their own sake, or just because GCC needs them? If you're only installing them for GCC then it's much easier to follow the method in the link above. > So you're suggesting using the same prefix for all of them. That would work, but if I screw-up a step in my install it's harder to untangle what I have to delete. No, where did I suggest that? 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. 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 Please read it. Carefully. I don't write those docs just to amuse myself. They realy will make it extremely easy to do what you're trying and failing to do. As it says at http://gcc.gnu.org/wiki/InstallingGCC "A major benefit of running srcdir/configure from outside the source directory (instead of running ./configure) is that the source directory will not be modified in any way, so if your build fails or you want to re-configure and build again, you simply delete everything in the objdir and start again." If you do what I'm suggesting then: 1) There are fewer steps to screw up 2) GCC automatically builds GMP, MPFR and MPC correctly, so you don't get a chance to screw that up 3) If you do screw up you just remove the entire build dir and start again, no uninstalling or figuring out what to remove. If you prefer to do it the hard way that's fine, but don't expect any more replies from me. I'm done trying to convince people to follow easy, foolproof steps, apparently everyone prefers to do things the hard way then ask why they couldn't get it to work. >> > This is what caused serious problems for me. Why would your build system look at prefix for dependencies? >> http://gcc.gnu.org/install/configure.html#with-as > Crazy, well ok now I know. 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. >> > I was looking for a --with-ld. It finally shows up in --help=recursive, but doesn't mention "linker" or anything I guess I was searching for. > Just a suggestion: maybe mention "linker" on that line. > ./ configure --help=recursive |grep linker |grep -v LDFLAGS| grep -v LIBS Feel free to open a bugzilla enhancement request. I'm not going to change it and nothing will get done by suggesting it on this list.