How to build a self-sufficient gcc/glibc/binutils set in a non-standard path?
Posted
by netvope
on Super User
See other posts from Super User
or by netvope
Published on 2010-06-06T11:53:28Z
Indexed on
2010/06/06
12:02 UTC
Read the original article
Hit count: 346
Suppose a set of custom-built gcc/glibc/binutils are in $prefix (e.g. /home/user/path)
I want:
gccto look for libraries in$prefix/lib64instead of/lib64gccto look for headers in$prefix/includeinstead of/include- to use
$prefix/lib64/ld-linux-x86-64.so.2as the (hard-coded) loader path instead of/lib64/ld-linux-x86-64.so.2 - the dynamic loader to look for shared libraries in
$prefix/lib64instead of/lib64
How should I configure the builds? Do I need to modify gcc's specs file or do anything else?
© Super User or respective owner