Ryan Oliver wrote:
> We all know what sysroot is for.
>
> All sysroot does is shift the search paths underneath the sysroot, no
> more, no less.
Well, yes. But Sysroot is specifically for *root* file systems. Here's
another data point from the GCC man/info/web docs:
"--sysroot=dir
Use dir as the logical *ROOT* directory for headers and libraries. For
example, if the compiler would normally search for headers in
/usr/include and libraries in /usr/lib, it will instead search
dir/usr/include and dir/usr/lib."
<emphasis is mine>
You're using sysroot on a non-root file system. Which is why you are
forced to hack the source to make it search only the dirs that you want.
I repeat - You're abusing the sysroot feature and setting a poor example.
> See clfs sysroot for a 1 pass build. If you want one for native builds,
> can post it.
I've already said the CLFS Sysroot build is closest in spirit to how
sysroot is meant to work. But
1) it's cross compilation and therefore useless as a mainstream build
2) it fails ICA verification dismally
Regards
Greg
--
http://www.diy-linux.org/
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
