|
From: NightStrike <nig...@gm...> - 2009-10-06 02:22:39
|
On Mon, Oct 5, 2009 at 6:28 AM, Keith Marshall <kei...@us...> wrote: > On Sunday 04 October 2009 22:43:07 NightStrike wrote: >> > > When you configure binutils, use the --with-sysroot option. >> > This is > how binutils (and gcc) should pretty much always be >> > built these days, > with the current configury system that is >> > present in sourceware's top > level configure. You point >> > binutils to the location of the sysroot, > and you get bonus >> > points if the sysroot is equal to or decendent from > your >> > prefix. >> > >> > This isn't true then? I understand from this that it doesn't >> > hurt to specify --with-sysroot if it is the same as --prefix. >> >> Sysroots aren't just for cross compiling anymore. > > Well, this is a direct contradiction of *current* GCC installation > instructions; http://gcc.gnu.org/install/configure.html says: Eh... It could use an update. > | ... > | Cross-Compiler-Specific Options > | > | The following options only apply to building cross compilers. > | > | --with-sysroot > | --with-sysroot=dir > | Tells GCC to consider dir as the root of a tree that contains a > | (subset of) the root filesystem of the target operating system. > | ... > > Rather meaningless, really, in the context of a native build. It depends on what you want to do. For instance, when you use sysroots, you get relative path linking, which allows for relocatable toolchains. That is, the end user can change the prefix to whatever he wants without having to rebuild the entire toolchain. This is essentially what the original post boils down to. |