Re: [linuxdc-dev] Newbie now having trouble with glibc

[M. R. B. <mr...@0x...>]

* Renegade Muskrat <dra...@sp...> on Sat, Sep 08, 2001:

> 
> Thank you much for the quick and accurate response. Glibc is compiling as i
> type this. I have another quick question, though. The documentation i've
> been reading on how to compile glibc suggests doing the following to
> actually install glibc once it is built:
> 
> touch iconv/iconv_prog login/pt_chown
> make install_root=${PREFIX} prefix="" install
> 
> Various instruction sets give slightly different options for the --prefix
> from the original glibc configure and for the install_root during the
> install. But basically it looks to me like they set the configure prefix to
> one thing, but then during the install place the files somewhere else. What
> is the point to doing this? Why not just set the --prefix in the configure
> to the final place to begin with?
>                                                -- Dan

In the binutils/gcc/glibc echelon, in your example (sh-linux) everything is
kept under /prefix/sh-linux/.  By default, ld looks for libraries and cpp
looks for headers in /prefix/sh-linux/sh-linux, as you can have multiple
sets of tools installed in the same prefix.  In your above line, your
install_root should actually be ${PREFIX}/sh-linux or cpp and ld won't be
able to find the includes and libs.  Also, don't forget to edit
${PREFIX}/sh-linux/lib/libc.so (once glibc is installed) and removed the
"/lib/" prefixes from the two filenames contained therein.

Note this is how you can *technically* install your cross-tools in /usr or
/usr/local, as all specific includes and libs will go under the
target-named subdir and gcc-specific stuff (libgcc.a, other crud) under
/prefix/lib/gcc-lib/sh-linux/<gcc version>/.  So *technically* you can
install 10 sets of cross-tools to varying targets and they can peacefully
coexist with your host gcc ... but you're always advised to choose an out
of the way prefix :P.

HTH,

M. R.