From: Grant Edwards <grante@visi.com>
To: Chris Gray <chris.gray@kiffer.be>
Cc: "Paul D. DeRocco" <pderocco@ix.netcom.com>,
eCos Discuss <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: eCos on 80186?
Date: Thu, 24 Jun 2004 14:01:00 -0000 [thread overview]
Message-ID: <20040624140143.GA15306@grante.dsl.visi.com> (raw)
In-Reply-To: <200406240817.18759.chris.gray@kiffer.be>
On Thu, Jun 24, 2004 at 08:17:18AM +0200, Chris Gray wrote:
> > 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.
Right, but we're talking about using a different compiler, not
a different make.
> 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).
Why would one even consider not using Gnu make? ecosconfig
already creates gnu makefiles automagically, and there's no
reason at all to try to port the project to an incompatible
version of make.
--
Grant Edwards
grante@visi.com
--
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 14:01 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
2004-06-24 11:40 ` Gregg C Levine
2004-06-24 14:01 ` Grant Edwards [this message]
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=20040624140143.GA15306@grante.dsl.visi.com \
--to=grante@visi.com \
--cc=chris.gray@kiffer.be \
--cc=ecos-discuss@ecos.sourceware.org \
--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).