This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
What about the file dates..... '2.17' could be near the last '2.16.91' :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?
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
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |