From: Chris Gray <chris.gray@kiffer.be>
To: Grant Edwards <grante@visi.com>,
"Paul D. DeRocco" <pderocco@ix.netcom.com>
Cc: eCos Discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: eCos on 80186?
Date: Thu, 24 Jun 2004 06:12:00 -0000 [thread overview]
Message-ID: <200406240817.18759.chris.gray@kiffer.be> (raw)
In-Reply-To: <20040624034404.GA12832@grante.dsl.visi.com>
On Thursday 24 June 2004 05:44, Grant Edwards wrote:
> On Wed, Jun 23, 2004 at 10:34:52PM -0400, Paul D. DeRocco wrote:
> > If you can find an old copy of Borland C++ Builder or earlier,
> > you could see what happens when you try to feed some eCos code
> > through it. My guess is that you'll have the biggest headaches
> > with the makefiles, rather than the C.
>
> Firstly, why would changing C compilers cause make to break?
Borland had their own version of make, and from what I remember (from my own
80186 days) it was pretty restricted even compared to standard un*x version
of make back then. It wouldn't have a snowflake in hell's chance of running a
makefile written for GNU make. So OP isn't going to be able to use Borland C+
+ Builder as such, only the compiler component (invoked from GNU make).
--
Chris Gray /k/ Embedded Java Solutions
Embedded & Mobile Java, OSGi http://www.kiffer.be/k/
chris.gray@kiffer.be +32 3 216 0369
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2004-06-24 6:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 15:24 [ECOS] " osrookie
2004-06-23 15:35 ` [ECOS] " Grant Edwards
2004-06-23 20:19 ` John Newlin
2004-06-24 2:35 ` [ECOS] " Paul D. DeRocco
2004-06-24 3:45 ` [ECOS] " Grant Edwards
2004-06-24 6:12 ` Chris Gray [this message]
2004-06-24 11:40 ` Gregg C Levine
2004-06-24 14:01 ` Grant Edwards
2004-06-24 12:12 AW: " Neundorf, Alexander
2004-06-24 14:26 ` Grant Edwards
2004-06-25 5:19 ` Mark Grosberg
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=200406240817.18759.chris.gray@kiffer.be \
--to=chris.gray@kiffer.be \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=grante@visi.com \
--cc=pderocco@ix.netcom.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).