How to build a self-sufficient gcc/glibc/binutils set in a non-standard path?
- by netvope
Suppose a set of custom-built gcc/glibc/binutils are in $prefix (e.g. /home/user/path)
I want:
gcc to look for libraries in $prefix/lib64 instead of /lib64
gcc to look for headers in $prefix/include instead of /include
to use $prefix/lib64/ld-linux-x86-64.so.2 as the (hard-coded) loader path instead of /lib64/ld-linux-x86-64.so.2
the dynamic loader to look for shared libraries in $prefix/lib64 instead of /lib64
How should I configure the builds? Do I need to modify gcc's specs file or do anything else?