This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


I did a complete rebuild of gcc adding that extra path statement and no
difference.

I dumped my entire build terminal output to a log file and scanned for the
text avr-gcc

the ONLY instance it ever shows avr-gcc is in that test which fails.
Testing for ANYTHING that generates a *gcc.exe, the only thing that comes up
is xgcc.exe as it is compiled:

  -DSTANDARD_STARTFILE_PREFIX=\"../../../\" -DSTANDARD_EXEC_PREFIX=\"/cygdri
ve/c
/avrgcc/lib/gcc-lib/\" -DDEFAULT_TARGET_VERSION=\"3.1.1\" -DDEFAULT_TARGET_M
ACHI
NE=\"avr\" -DSTANDARD_BINDIR_PREFIX=\"/cygdrive/c/avrgcc/bin/\" -DTOOLDIR_BA
SE_P
REFIX=\"../../../../\" `test "X${SHLIB_LINK}" = "X" || test "yes" != "yes"
|| ec
ho "-DENABLE_SHARED_LIBGCC"` `test "X${SHLIB_MULTILIB}" = "X" || echo
"-DNO_SHAR
ED_LIBGCC_MULTILIB"` \
  -c ../../gcc/gccspec.c -o gccspec.o)
i686-pc-mingw32-gcc -DIN_GCC -DCROSS_COMPILE   -g -O2 -W -Wall -Wwrite-strin
gs -
Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-lo
ng
-DHAVE_CONFIG_H  -o xgcc.exe gcc.o gccspec.o intl.o \
  prefix.o version.o    ../libiberty/libiberty.a
i686-pc-mingw32-gcc -c -DIN_GCC -DCROSS_COMPILE   -g -O2 -W -Wall -Wwrite-st
ring
s -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long
-lon
g  -DHAVE_CONFIG_H    -I. -I. -I../../gcc -I../../gcc/. -I../../gcc/config -
I../
../gcc/../include ../../gcc/cppmain.c -o cppmain.o
i686-pc-mingw32-gcc -DIN_GCC -DCROSS_COMPILE   -g -O2 -W -Wall -Wwrite-strin
gs -
Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-lo
ng
-DHAVE_CONFIG_H  -o cpp0.exe cppmain.o \
intl.o libcpp.a   ../libiberty/libiberty.a
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

Thanks,
Tony

----- Original Message -----
From: "Marcel Telka" <marcel@telka.sk>
To: <crossgcc@sources.redhat.com>
Sent: Thursday, June 13, 2002 2:40 PM
Subject: Re: Host:Mingw Target:avr Build:Cygwin more detailed problem
description


> On Thu, Jun 13, 2002 at 11:16:25AM -0400, Tony Mahar wrote:
> > 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
>
> Try add this line here:
>
> export PATH=$PATH:$prefixdir/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
> > this:
> >
../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
> > specifications?
> >
> > 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!
>
>
> Regards.
>
> --
> +-------------------------------------------+
> | Marcel Telka   e-mail:   marcel@telka.sk  |
> |                homepage: http://telka.sk/ |
> |                jabber:   marcel@jabber.sk |
> +-------------------------------------------+
>
> ------
> Want more information?  See the CrossGCC FAQ,
http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to
crossgcc-unsubscribe@sources.redhat.com
>


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]