Failed build of AVR cross-compiler with combined tree

Failed build of AVR cross-compiler with combined tree

[Ulf Magnusson]

I downloaded the binutils-2.17 and gcc-3.4.6 distributions and
attempted to build a cross-compiler for AVR using the following:

tar -xvjf binutils-2.17.tar.bz2
tar -xvjf gcc-3.4.6.tar.bz2
mkdir combined-tree && cd combined_tree
../binutils-2.17/symlink-tree ../gcc-3.4.6
../binutils-2.17/symlink-tree ../binutils-2.17
mkdir ../build && cd ../build
../combined_tree/configure --target=avr --enable-languages=c
--prefix=/home/ulf/devel/avr/avr-gcc

The configuration step seems to go through fine, but after issuing
'make', the build process fails with the following error:

make[2]: Entering directory '/home/ulf/devel/avr/gcc/build/gcc'
./gengtype
../../combined-tree/gcc/../include/hashtab.h:111: syntax error,
unexpected ',', expecting '('
make[2]: *** [s-gtype] Error 1

Could the problem be that I'm combining versions of gcc and binutils
that should not be mixed? What versions are "safe" to combine in that
case?

Should I report this as a bug?

/Ulf Magnusson

Re: Failed build of AVR cross-compiler with combined tree

[Kai Ruottu]

Ulf Magnusson hade skrivit:
> I downloaded the binutils-2.17 and gcc-3.4.6 distributions and
> attempted to build a cross-compiler for AVR using the following:
>
> tar -xvjf binutils-2.17.tar.bz2
> tar -xvjf gcc-3.4.6.tar.bz2
> mkdir combined-tree && cd combined_tree
> .../binutils-2.17/symlink-tree ../gcc-3.4.6
> .../binutils-2.17/symlink-tree ../binutils-2.17
> mkdir ../build && cd ../build
> .../combined_tree/configure --target=avr --enable-languages=c
> --prefix=/home/ulf/devel/avr/avr-gcc
>
> The configuration step seems to go through fine, but after issuing
> 'make', the build process fails with the following error:
>
> make[2]: Entering directory '/home/ulf/devel/avr/gcc/build/gcc'
> ../gengtype
> .../../combined-tree/gcc/../include/hashtab.h:111: syntax error,
> unexpected ',', expecting '('
> make[2]: *** [s-gtype] Error 1
What about the file dates..... '2.17' could be near the last '2.16.91' :

Dell:/data1/home/src/gcc-3.4.6 # l include/hashtab.h
-rw-rw-r-- 1 515 515 6835 2003-05-07 23:30 include/hashtab.h
Dell:/data1/home/src/gcc-3.4.6 # l ../binutils-2.16.91/include/hashtab.h
-rw-r--r-- 1 root root 7264 2005-11-18 12:36 
../binutils-2.16.91/include/hashtab.h

More than 2 years difference!  The "in-sync with gcc-3.4.6" binutils 
must be much
older, what about '2.14.90' ('2.15') :

Dell:/data1/home/src/gcc-3.4.6 # l ../binutils-2.14.90/include/hashtab.h
-rw-r--r-- 1 root root 6835 2003-06-04 22:04 
../binutils-2.14.90/include/hashtab.h

This file really was identical but there were differences, sometimes the GCC
sources having a newer file, sometimes the binutils, in the 'include' 
(alone)...
> Could the problem be that I'm combining versions of gcc and binutils
> that should not be mixed? What versions are "safe" to combine in that
> case?
 Using 'diff' between the common directories could tell which binutils and
GCC releases could be near enough....
> Should I report this as a bug?
 No....  The FSF binutils and  GCC releases should be keeped as separate 
and be separately
built :-(

 If you want to play with an already "in-sync" Cygnus/RedHat toolchain, 
something like the :

ftp.funet.fi/pub/linux/mirrors/redhat/redhat/gnupro/AM33/am33-04r2-2/tools/src-cross.tar.bz2 


could be suitable, its binutils version is "2.15-am33-04r2-2", 
GCC-version "3.4-am33-04r2-2"
and GDB version is "6.21-am33-04r2-2".  Of course you can edit these to 
reprent your own
"brand" (For instance by changing the "am33" to "avr" :-).  The 
'gcc/version.c' has that GCC
string, the 'gdb/version.in' the GDB one and the 'bfd/configure' the 
binutils one....

Maybe somewhere is a newer "src-cross" archive... Is "Kuukkeli" (Google 
in english, annat på
svenska)" aware about this, hmmm :

   
http://sunsite.utk.edu/ftp/tigerd2/redhat/redhat/gnupro/AM33/am33-04r2-4/tools/

This seems to be from this year...