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

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

>> CC="${TARGET}-gcc -ml -m4" ../glibc-2.2.2/configure \
>>      --host=${HOST} --build=${HOST} --target=${TARGET} \
>>      --prefix=${PREFIX}/${TARGET} --enable-add-ons \
>>      --with-headers=${PREFIX}/linux/include \
>>      --with-binutils=${PREFIX}/bin \
>>      2>&1 | tee -a configure.out
>> make -w all \
>>      2>&1 | tee -a make.out
>> 
>> 
>This would very likely be breaking because TARGET=HOST in glibc.. so you're
>essentially building an i686-pc-linux-gnu glibc with your sh-linux version of
>gcc -- no good can come of that.
>
>Change your --host=${HOST} to --host=${TARGET} and try again..

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
  --------------------------------------------------------------------
            "I'm still sane on three planets and two moons."
  --------------------------------------------------------------------
      Daniel Ramaley                  3118 Cottage Grove Ave Apt 8
      dramaley at spatulacity dot cx        Des Moines, Iowa 50311
      http://www.spatulacity.cx/                    (515) 271-5233
  --------------------------------------------------------------------
       WARNING: REDISTRIBUTION OF THIS MESSAGE MAY BE IN
                VIOLATION OF APPLICABLE COPYRIGHT LAWS.
                THIS MESSAGE NOT GUARANTEED Y-TO-K COMPLIANT.