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

[Renegade M. <dra...@sp...>]

>> 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?
>
>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.

This sort of makes sense. I originally configured glibc with
--prefix=${PREFIX}/${TARGET} (where PREFIX is /usr/local/sh-linux and
TARGET is sh-linux). So then should i still set install_root to
/usr/local/sh-linux/sh-linux (which is the same as the configure prefix i
originally used) and prefix to an empty string?


Incidentally, it doesn't really matter yet since glibc still managed to hit
a compile error last night. This morning i'm trying again with slightly
different options (i changed the configure prefix from ${PREFIX}/${TARGET}
to ${PREFIX} and will see if that matters).