Re: unable to build glibc-2.2.5 with gcc-3.1 for ARM

[jeroen dobbelaere <jeroen dot dobbelaere at acunia dot com>]

Hi,


> ok, so after fixing the glibc build problem that everyone pointed out to
> me, i finally get all the pieces built and in place.  then, i go back to 
> rebuild gcc-3.1, and now that's complaining...
> 
> after glibc install, i start a new directory to build the final gcc into,
> and use this configure command:
> 
> ../gcc-3.1/configure --prefix=/usr/local/arm-v4l-linux/ --target=arm-v4l-linux --with-cpu=strongarm110 --program-transform-names=s,^,arm-v4l-linux-, --without-fp --with-softfloat-support=internal --enable-threads=posix --with-headers=/usr/local/arm-v4l-linux/include/
> 
> then, during build, it chugs along for a good while before stopping here:
> 
> mv libgcc/./tmp-libgcc.map libgcc/./libgcc.map
> /tmp/skiff/new-gcc31/gcc-build-p2/gcc/xgcc -B/tmp/skiff/new-gcc31/gcc-build-p2/gcc/ -B/usr/local/arm-v4l-linux//arm-v4l-linux/bin/ -B/usr/local/arm-v4l-linux//arm-v4l-linux/lib/ -isystem /usr/local/arm-v4l-linux//arm-v4l-linux/include -O2  -DIN_GCC -DCROSS_COMPILE   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include  -fomit-frame-pointer -fPIC -g0 -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  -shared -nodefaultlibs -Wl,--soname=libgcc_s.so.1 -Wl,--version-script=libgcc/./libgcc.map -o libgcc_s.so.1   libgcc/./_udivsi3.o libgcc/./_divsi3.o libgcc/./_umodsi3.o libgcc/./_modsi3.o libgcc/./_dvmd_lnx.o libgcc/./_muldi3.o libgcc/./_negdi2.o libgcc/./_lshrdi3.o libgcc/./_ashldi3.o libgcc/./_ashrdi3.o libgcc/./_ffsdi2.o libgcc/./_clz.o libgcc/./_cmpdi2.o libgcc/./_ucmpdi2.o libgcc/./_floatdidf.o libgcc/./_floatdisf.o libgcc/./_fixunsdfsi.o libgcc/./_fixunssfsi.o libgcc/./_fixunsdfdi.o libgcc/./_fixdfdi.o libgcc/./_fixunssfdi.o libgcc/.
/!
> _fixsfdi.o libgcc/./_fixxfdi.o libgcc/./_fixunsxfdi.o libgcc/./_floatdixf.o libgcc/./_fixunsxfsi.o libgcc/./_fixtfdi.o libgcc/./_fixunstfdi.o libgcc/./_floatditf.o libgcc/./_clear_cache.o libgcc/./_trampoline.o libgcc/./__main.o libgcc/./_exit.o libgcc/./_absvsi2.o libgcc/./_absvdi2.o libgcc/./_addvsi3.o libgcc/./_addvdi3.o libgcc/./_subvsi3.o libgcc/./_subvdi3.o libgcc/./_mulvsi3.o libgcc/./_mulvdi3.o libgcc/./_negvsi2.o libgcc/./_negvdi2.o libgcc/./_ctors.o libgcc/./_divdi3.o libgcc/./_moddi3.o libgcc/./_udivdi3.o libgcc/./_umoddi3.o libgcc/./_udiv_w_sdiv.o libgcc/./_udivmoddi4.o  libgcc/./unwind-dw2.o libgcc/./unwind-dw2-fde-glibc.o libgcc/./unwind-sjlj.o -lc && rm -f libgcc_s.so && ln -s libgcc_s.so.1 libgcc_s.so
> /usr/local/arm-v4l-linux//arm-v4l-linux/bin/ld: cannot open crti.o: No such file or directory
> collect2: ld returned 1 exit status
> make[2]: *** [libgcc_s.so] Error 1
> 
> any insights on this?  sorry to pester the list with such questions, but
> i'm not sure where else to go with them.
> 
> thanks,
> 
> josh
> 

What I have as directory structure for cross compilation is this :

suppose I'm cross-compiling for a 'arm-linux' target with prefix=/usr/local/arm-linux/

headers for arm-linux should go into '/usr/local/arm-linux/arm-linux/include'
(note the 'arm-linux/arm-linux' part -> $(DESTINATION)/$(TARGET)/include)


binutils and gcc should be configured with :
   --prefix=/usr/local/arm-linux --target=arm-linux

arm-linux specific libraries will be put in :
/usr/local/arm-linux/arm-linux/lib (!!)

glibc should be configured with
   --prefix=/usr/local/arm-linux/arm-linux

because the libraries created are specific for arm-linux

with this structure,
  /usr/local/arm-linux/lib should only contain 'host' (ex. i386) specific libraries,
and
  /usr/local/arm-linux/arm-linux/lib should contain 'target' (ex. arm-linux) libraries.


Greetings,
-- 
Jeroen Dobbelaere
Embedded Software Engineer

ACUNIA Embedded Solutions
http://www.acunia.com/aes