[Patch] CT 0.3 - glibc-2.2.5-allow-gcc-4.0-mipsel

[Piete Sartain]

Thanks for the responses, I don't know how much some of this affects 
what I'm doing (I know it *shouldn't*, but that's never the same as 
*doesn't*), but I'll detail it anyway.

To Arno:
> Did you use crosstool.sh, or otherwise made sure that 
> mipsel-unknown-linux-gnu-as is in your path? 

I used crosstool-0.30, but so as not to pollute the original directory 
(beyond all reason), and so I can keep a record of what I've done, I run 
it from a separate script.

The file heirarchy I use appears thus:

 > ls ~/src/crosstool/  [directories only]

	build/
	crosstool@	--> crosstool-0.30
	crosstool-0.28-rc37
	crosstool-0.30
	patches/
	scripts/
	tarballs/

All my scripts are kept in "scripts", all the patches I've got/made from 
elsewhere (and fiddled with) are in "patches", source tars are in 
tarballs and build is used when i need to do something by hand.

The script I'm using to run looks pretty much like you'd expect:

#!/bin/sh
set -ex
# Little-endian MIPS

CROSSTOOL_DIR=$HOME/src/crosstool
TARBALLS_DIR=$CROSSTOOL_DIR/tarballs
RESULT_TOP=/opt/crosstool
export TARBALLS_DIR RESULT_TOP
GCC_LANGUAGES="c,c++"
export GCC_LANGUAGES

# Unset LD_LIBRARY_PATH so glibc can build
LD_LIBRARY_PATH=
export LD_LIBRARY_PATH

# cd into crosstool directory
cd $CROSSTOOL_DIR/crosstool

# clear working area
#rm $CROSSTOOL_DIR/build/* -dRf

# Build the toolchain.
  eval `cat mipsel.dat gcc-4.0-20050305-glibc-2.2.5.dat` sh all.sh --notest
#  eval `cat mipsel.dat gcc-3.3.4-glibc-2.3.2.dat` sh all.sh --notest


> This looks like gcc's configure could not find the correct assembler 
> in the path. Either that, or the options [target-]as takes have 
> changed recently and the gcc and binutils versions you are currently
>  using are incompatible...

crosstool/build/mipsel-unknown-linux-gnu/gcc4-...glibc-2.2.5/build-gcc-core 
/config.log shows this:

  ...
configure:3673: checking for i686-host_pc-linux-gnu-as
configure:3706: checking for as
  ...
configure:4328: checking for mipsel-unknown-linux-gnu-as
  ...

> Check gcc's config.log for the line "checking for 
> mipsel-unknown-linux-gnu-as... <result>"
> 

build-gcc-core/gcc/config.log gives me:

  ...
PATH: 
/opt/crosstool/mipsel-unknown-linux-gnu/gcc-4.0-20050305-glibc-2.2.5/bin
  ...
configure:1469: checking target system type
configure:1483: result: mipsel-unknown-linux-gnu
configure:1549: checking LIBRARY_PATH variable
configure:1559: result: ok
configure:1580: checking GCC_EXEC_PREFIX variable
configure:1590: result: ok
configure:1691: checking whether to place generated files in the source 
directory
configure:1701: result: no
configure:1747: checking whether a default linker was specified
configure:1758: result: no
configure:1807: checking whether a default assembler was specified
configure:1818: result: no
  ...
configure:12748: checking what assembler to use
configure:12871: result: 
/opt/crosstool/mipsel-unknown-linux-gnu/gcc-4.0-20050305-glibc-2.2.5/mipsel-unknown-linux-gnu/bin/as
  ...
gcc_cv_as=/opt/crosstool/mipsel-unknown-linux-gnu/gcc-4.0-20050305-glibc-2.2.5/mipsel-unknown-linux-gnu/bin/as
  ...

Which looks to me like it's ok, and using the right bits & pieces.


To Dan:

http://gcc.gnu.org/ml/gcc/2004-08/msg00172.html shows that this guys 
problem lay in a difference of prefix and target options in binutils & 
gcc.  I don't think it's possible for crosstool to give two different 
options, is it?

I'm rebuilding now, just to verify that I didn't mess up somewhere along 
the line.  I'll keep you all posted.

  - Piete.

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com