Host:Mingw Target:avr Build:Cygwin more detailed problem description

Tony Mahar
Thu Jun 13 08:16:00 GMT 2002

Hey guys,

Well, after going over the faq again and making some slight changes I still
get the same problems...
I am compiling under cygwin and this is how I have my environment setup:

export host=i686-pc-mingw32
export target=avr
export build=i686-pc-cygwin
export prefixdir=/cygdrive/c/avrgcc
export PATH=$PATH:/cygdrive/c/mingw/bin

I configure the latest CVS snapshot of BINUTILS from a build-binutils sub
dir with this:
../configure --host=$host --target=$target --build=$build --prefix=$prefixdi
r --program-prefix="avr-" --disable-nls

binutils compiles and the tools run great! (as they always have)

I configured the latest CVS snapshot of GCC from the build-gcc sub dir with
../configure --host=$host --target=$target --build=$build --prefix=$prefixdi
r --program-prefix="avr-" --disable-nls --enable-languages="c"

gcc compiles cleanly until it reaches the point where I guess it tests it's

make[1]: Leaving directory `/usr/local/gcc-20020610/build-gcc/libiberty'
make[1]: Entering directory `/usr/local/gcc-20020610/build-gcc/gcc'
(cd intl && make all)
make[2]: Entering directory `/usr/local/gcc-20020610/build-gcc/gcc/intl'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/local/gcc-20020610/build-gcc/gcc/intl'
avr-gcc -dumpspecs > tmp-specs
avr-gcc: not found
make[1]: *** [specs] Error 127
make[1]: Leaving directory `/usr/local/gcc-20020610/build-gcc/gcc'
make: *** [all-gcc] Error 2

I dont understand how it could cleanly build everything, not reporting any
errors creating avr-gcc, and then not have it exist!

Any help would greatly be appreciated!


Want more information?  See the CrossGCC FAQ,
Want to unsubscribe? Send a note to

More information about the crossgcc mailing list