From: Rib Rdb <ribrdb@ribrdb.com>
To: Gary Thomas <gary@chez-thomas.org>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Building from OS X
Date: Tue, 11 Nov 2003 00:27:00 -0000 [thread overview]
Message-ID: <BF4C6284-13DD-11D8-A06A-000393C4B0B6@ribrdb.com> (raw)
In-Reply-To: <1068496486.9906.71.camel@hermes>
What would be the proper way to build it. Configure complains about an
unknown host type unless I lie and say --host=powerpc-apple-linux
instead of powerpc-apple-darwin.
Should I just configure as linux and then edit the generated makefiles?
On Monday, November 10, 2003, at 12:34 PM, Gary Thomas wrote:
> On Mon, 2003-11-10 at 13:28, Rib Rdb wrote:
>> Since the configuration tool won't build on OS X, would it work to
>> configure and build eCos on a windows machine, then copy the libraries
>> and headers to a Mac OS X machine and do the development there with
>> the
>> appropriate cross compilers? Also, would the version of gcc, etc used
>> on the Mac have to be the same as on the Windows computer?
>
> Or, just use 'ecosconfig' on your Mac! which surely will build.
>
> There's no reason you absolutely have to use the Config Tool.
>
> --
> Gary Thomas <gary@chez-thomas.org>
>
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-11-11 0:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 20:28 Rib Rdb
2003-11-10 20:34 ` Gary Thomas
2003-11-10 22:00 ` [ECOS] Deciphering ISO C (Chap 6.3.2.3 - Pointers) Philip Soeberg
[not found] ` <E1AJK5Y-0004tk-00@londo.lunn.ch>
2003-11-10 22:16 ` Andrew Lunn
2003-11-11 0:27 ` Rib Rdb [this message]
2003-11-11 0:37 ` [ECOS] Building from OS X Gary Thomas
2003-11-11 0:49 ` Rib Rdb
2003-11-11 1:18 ` Rib Rdb
2003-11-13 9:37 ` [ECOS] " John Dallaway
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=BF4C6284-13DD-11D8-A06A-000393C4B0B6@ribrdb.com \
--to=ribrdb@ribrdb.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=gary@chez-thomas.org \
/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).