From: Ian Lance Taylor <ian@cygnus.com>
To: joel@OARcorp.com
Cc: gas2@cygnus.com
Subject: Re: i386-go32 problem in gas-971208
Date: Thu, 11 Dec 1997 08:35:00 -0000 [thread overview]
Message-ID: <199712111635.LAA27755@subrogation.cygnus.com> (raw)
In-Reply-To: <Pine.BSF.3.96.971211090129.22102H-100000@vespucci.advicom.net>
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
next prev parent reply other threads:[~1997-12-11 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-11 7:01 Joel Sherrill
1997-12-11 8:35 ` Ian Lance Taylor [this message]
1997-12-11 9:00 ` Joel Sherrill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199712111635.LAA27755@subrogation.cygnus.com \
--to=ian@cygnus.com \
--cc=gas2@cygnus.com \
--cc=joel@OARcorp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).