RE: Cygwin GCC cross-compile build problem

[Keith Zambrano <Keith dot Zambrano at GE-interlogix dot com>]

All,
    I was successful in compiling crossGCC on Cygwin by using the tar
package from the Bill Gatliff website. Apparently the Cygwin tarballs have a
problem.

>  -----Original Message-----
> From: 	Keith Zambrano  
> Sent:	Wednesday, August 14, 2002 4:15 PM
> To:	'CrossGcc@sources.redhat.com'
> Subject:	Cygwin GCC cross-compile build problem
> 
> Hi, 
>   I am attempting to build a cross compiler for an ARM target using Cygwin
> (which is possible base on the mailing lists). I obtained the tar packages
> from the Cywin installation.
> 
>   I have used various HOW-TOs ( W. A. Gatliff, CrossGCC FAQ...) with the
> same results. I have successfully built and installed binutils20010706 and
> configured gcc-3.1.1-4. However MAKE gets stuck in the gcc/intl directory
> forking shells until the PC dies. The following is a clip from the log
> file ( killed it before the PC died):
> 
> make[3]: Entering directory `/src/gcc-3.1.1-4/build/gcc'
> (cd intl && make all)
> make[4]: Entering directory `/src/gcc-3.1.1-4/build/gcc/intl'
> make[4]: Nothing to be done for `all'.
> make[4]: Leaving directory `/src/gcc-3.1.1-4/build/gcc/intl'
> test -d po || mkdir po
> : --statistics -o po/da.gmo ../../gcc/po/da.po
> test -d po || mkdir po
> : --statistics -o po/el.gmo ../../gcc/po/el.po
> test -d po || mkdir po
> : --statistics -o po/es.gmo ../../gcc/po/es.po
> test -d po || mkdir po
> : --statistics -o po/fr.gmo ../../gcc/po/fr.po
> test -d po || mkdir po
> : --statistics -o po/ja.gmo ../../gcc/po/ja.po
> test -d po || mkdir po
> : --statistics -o po/nl.gmo ../../gcc/po/nl.po
> test -d po || mkdir po
> : --statistics -o po/sv.gmo ../../gcc/po/sv.po
> test -d po || mkdir po
> : --statistics -o po/tr.gmo ../../gcc/po/tr.po
> make GCC_FOR_TARGET="/src/gcc-3.1.1-4/build/gcc/xgcc
> -B/src/gcc-3.1.1-4/build/gcc/ -B/armCross/arm-elf/bin/
> -B/armCross/arm-elf/lib/ -isystem /armCross/arm-elf/include" \
>   HOST_PREFIX="" HOST_PREFIX_1="loser-" \
>   AR_FOR_TARGET="arm-elf-ar" \
>   AR_CREATE_FOR_TARGET="arm-elf-ar  rc" \
>   AR_FLAGS_FOR_TARGET="" \
>   CFLAGS="-g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes
> -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -W -Wall
> -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional
> -pedantic -Wno-long-long -W -Wall -Wwrite-strings -Wstrict-prototypes
> -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long" \
>   RANLIB_FOR_TARGET="arm-elf-ranlib" \
>   RANLIB_TEST_FOR_TARGET="[ -f arm-elf-ranlib ] || ( [ i686-pc-cygwin =
> arm-unknown-elf ] && [ -f /usr/bin/ranlib -o -f /bin/ranlib ] )" \
>   NM_FOR_TARGET="arm-elf-nm" AWK="gawk" \
>   LIBGCC2_CFLAGS="-O2  -DIN_GCC -DCROSS_COMPILE   -W -Wall -Wwrite-strings
> -Wstrict-prototypes -Wmissing-prototypes -isystem ./include
> -Dinhibit_libc -fno-inline -g  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED
> -Dinhibit_libc" \
>   INCLUDES="-I. -I. -I../../gcc -I../../gcc/. -I../../gcc/config
> -I../../gcc/../include" 
> make[4]: Entering directory `/src/gcc-3.1.1-4/build/gcc'
> (cd intl && make all)
> make[5]: Entering directory `/src/gcc-3.1.1-4/build/gcc/intl'
> make[5]: Nothing to be done for `all'.
> make[5]: Leaving directory `/src/gcc-3.1.1-4/build/gcc/intl'
> test -d po || mkdir po
> : --statistics -o po/da.gmo ../../gcc/po/da.po
> test -d po || mkdir po
> : --statistics -o po/el.gmo ../../gcc/po/el.po
> test -d po || mkdir po
> : --statistics -o po/es.gmo ../../gcc/po/es.po
> test -d po || mkdir po
> : --statistics -o po/fr.gmo ../../gcc/po/fr.po
> test -d po || mkdir po
> : --statistics -o po/ja.gmo ../../gcc/po/ja.po
> test -d po || mkdir po
> : --statistics -o po/nl.gmo ../../gcc/po/nl.po
> test -d po || mkdir po
> : --statistics -o po/sv.gmo ../../gcc/po/sv.po
> test -d po || mkdir po
> : --statistics -o po/tr.gmo ../../gcc/po/tr.po
> make[3]: *** [stmp-multilib] Interrupt
> make[2]: *** [stmp-multilib] Interrupt
> make[1]: *** [stmp-multilib] Interrupt
> make: *** [all-gcc] Interrupt
> 
> Can anyone point me in the right direction? Thanks.
> 

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