From: James E Wilson <wilson@specifixinc.com>
To: Tal Agmon <Tal.Agmon@nsc.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Canadian cross on cygwin
Date: Tue, 31 Aug 2004 01:06:00 -0000 [thread overview]
Message-ID: <1093912102.7528.57.camel@aretha.corp.specifixinc.com> (raw)
In-Reply-To: <OF016B6C89.0C9CF256-ONC2256EFC.002C7BEF-C2256EFC.002D48B0@nsc.com>
On Thu, 2004-08-26 at 01:12, Tal Agmon wrote:
> Isn't compiling a compiler that is going to generate crx executable, will run
> on windows and built on cygwin is a canadian cross?
cygwin does run on windows, so it isn't clear what you mean here.
The easy solution here is that you build a --target=crx-elf compiler.
This will give you a cygwin cross compiler to crx-elf. Anyone with
cygwin can run it, and perhaps all they need is the cygwin dll, though
it doesn't hurt to give them an entire cygwin environment.
If you won't want to use the cygwin dll, then one wonders why you are
using cygwin at all. Using mingw32 to build a --target=crx-elf
compiler, and you will get a mingw32 cross compiler to crx-elf.
Assuming that mingw32 can build gcc. I don't have any experience with
mingw32, so I don't know what its capabilities are.
Trying to build a canadian cross cygwin build/mingw32 host/crx-elf
target is probably a lot of unnecessary complexity. Building canadian
crosses takes a lot of time and effort to get right. Don't waste your
time doing it if you really don't need to.
Configuring for a windows host makes no sense. If gcc could be built
natively, then we wouldn't need cygwin or mingw32 in the first place.
If you need help dealing with cygwin/mingw32 issues, then you are
probably better off asking on a cygwin or mingw32 mailing list. We can
only help you with gcc issues.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2004-08-31 0:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 9:58 Tal Agmon
2004-08-31 1:06 ` James E Wilson [this message]
2004-09-01 13:43 ` [OT] " Dave Korn
-- strict thread matches above, loose matches on Subject: below --
2004-08-25 17:38 Tal Agmon
2004-08-25 23:47 ` Mike Stump
2004-08-26 0:13 ` James E Wilson
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=1093912102.7528.57.camel@aretha.corp.specifixinc.com \
--to=wilson@specifixinc.com \
--cc=Tal.Agmon@nsc.com \
--cc=gcc@gcc.gnu.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).