This is the mail archive of the gas2@sourceware.cygnus.com mailing list for the gas2 project.

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

Re: i386-go32 problem in gas-971208

   Date: Thu, 11 Dec 1997 09:01:48 -0600 (CST)
   From: Joel Sherrill <joel@OARcorp.com>

   I recently switched from binutils 2.8.1 to gas-971208 and ran into the
   following problem building for i386-go32-rtems:

   Testing libgcc1.  Ignore linker warning messages.
   /usr1/rtems/work/tools/build-i386-go32-tools/gcc/xgcc
   -B/usr1/rtems/work/tools/build-i386-go32-tools/gcc/ -DCROSS_COMPILE
   -DIN_GCC    -O2 -g -I./include  libgcc1-test.o -o libgcc1-test \
     -nostartfiles -nostdlib
   `/usr1/rtems/work/tools/build-i386-go32-tools/gcc/xgcc
    -B/usr1/rtems/work/tools/build-i386-go32-tools/gcc/
   --print-libgcc-file-name`
   /usr1/rtems/work/tools/build-i386-go32-tools/gcc/collect-ld: target
   coff-go32-exe not found
   collect2: ld returned 1 exit status

   The same build procedure worked fine for 2.8.1.  Any ideas what broke?

It means that the linker tried to create a BFD of type coff-go32-exe,
but that BFD type was not defined.

The go32 code was changed around by Robert Hoehne
<robert.hoehne@Mathematik.TU-Chemnitz.DE>.  Part of that change was to
change the target name used by go32 to i386-pc-msdosdjgpp.  This
doesn't work well with the RTEMS configuration triplet of
i386-go32-rtems.

Actually, a triplet of i386-go32-rtems doesn't make much sense to me,
now that I think about it.  I'm not sure what it is supposed to mean.
i386-*-rtems should have a single object file format.  If you want to
support a different object file format, you should have a target like
i386-*-rtemself or whatever.

The snapshot isn't working because ld and bfd treat the
i386-go32-rtems target differently.

Ian