This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: h8300-coff build error with gcc-3.5-20040704
- From: "Dave Korn" <dk at artimi dot com>
- To: "'Nitin Shah'" <NitinS2 at KPITCummins dot com>,<gcc at gnu dot org>
- Date: Wed, 14 Jul 2004 16:31:19 +0100
- Subject: RE: h8300-coff build error with gcc-3.5-20040704
> -----Original Message-----
> From: gcc-owner On Behalf Of Nitin Shah
> Sent: 14 July 2004 07:10
> In the latest GCC (gcc-3.5-20040704), binutils
> (binutils-040628) snapshots and newlib-1.12.0, while building
> toolchain for target h8300-coff I am getting error as mention
> below at the stage of final gcc make. Kindly suggest how to
> remove this error.
> /tmp/cc4dWn8b.s: Assembler messages:
> /tmp/cc4dWn8b.s:16: Error: junk at end of line, first
> unrecognized character is `i'
> /tmp/cc4dWn8b.s:20: Error: junk at end of line, first
> unrecognized character is `i'
> /tmp/cc4dWn8b.s:24: Error: junk at end of line, first
> unrecognized character is `u'
> /tmp/cc4dWn8b.s:28: Error: junk at end of line, first
> unrecognized character is `l'
> /tmp/cc4dWn8b.s:32: Error: junk at end of line, first
> unrecognized character is `l'
> /tmp/cc4dWn8b.s:36: Error: junk at end of line, first
> unrecognized character is `l'
> /tmp/cc4dWn8b.s:40: Error: junk at end of line, first
> unrecognized character is `l'
> /tmp/cc4dWn8b.s:44: Error: junk at end of line, first
> unrecognized character is `i'
> /tmp/cc4dWn8b.s:48: Error: junk at end of line, first
> unrecognized character is `u'
> /tmp/cc4dWn8b.s:52: Error: junk at end of line, first
> unrecognized character is `s'
> /tmp/cc4dWn8b.s:56: Error: junk at end of line, first
> unrecognized character is `c'
> /tmp/cc4dWn8b.s:60: Error: junk at end of line, first
> unrecognized character is `c'
> /tmp/cc4dWn8b.s:72: Error: junk at end of line, first
> unrecognized character is `d'
> make[3]: *** [testsuite_abi.o] Error 1
Ninety-nine times out of a hundred, when you see an error where the
assembler is complaining that the compiler-generated files are gibberish,
and you're building a cross-compiler, you've got your path setting wrong,
and either the native assembler is being called to assemble files for the
cross-target, or vice-versa.
In this particular case, I think you most likely forgot to add the new
cross-binutils to your path after you built and installed them. You want to
say
export PATH=${PREFIX}/bin:$PATH
where ${PREFIX} is the setting you supplied on the binutils command line to
the --prefix= option, i.e. the directory where "make install" places the new
cross-binutils subdirectories.
cheers,
DaveK
--
Can't think of a witty .sigline today....