From: Joel Sherrill <joel@OARcorp.com>
To: Ian Lance Taylor <ian@cygnus.com>
Cc: gas2@cygnus.com
Subject: Re: i386-go32 problem in gas-971208
Date: Thu, 11 Dec 1997 09:00:00 -0000 [thread overview]
Message-ID: <Pine.BSF.3.96.971211105340.22102I-100000@vespucci.advicom.net> (raw)
In-Reply-To: <199712111635.LAA27755@subrogation.cygnus.com>
On Thu, 11 Dec 1997, Ian Lance Taylor wrote:
>
> 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.
Got it. It is compiling OK now.
> 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.
RTEMS has a bunch of what I call "normal" configurations and a handful of
oddities. It is the oddities I have trouble naming.
i386-go32-rtems is based on djgpp v1 (yes old) and uses the go32 dos
extender to go into protected mode and kick off the rtems application. It
requires slightly different newlib configuration and crt0.o as well as
some support libraries from the djgpp distribution. This toolset
configuration is subtly different from the vanilla embedded i386-rtems
configuration. I really do not know what this one should be named.
This ignores the harder rtems configurations like the ports to unix
(solaris, linux, and hpux) where you can test rtems applications without
a cpu simulator or real hw. :)
--joel
prev parent reply other threads:[~1997-12-11 9:00 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
1997-12-11 9:00 ` Joel Sherrill [this message]
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=Pine.BSF.3.96.971211105340.22102I-100000@vespucci.advicom.net \
--to=joel@oarcorp.com \
--cc=gas2@cygnus.com \
--cc=ian@cygnus.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).