From: Ted Byers <r.ted.byers@rogers.com>
To: Rick Mann <rmann@latencyzero.com>, gcc-help@gcc.gnu.org
Subject: Re: Should I be able to build cross gcc 4.x on Cygwin?
Date: Tue, 11 Dec 2007 23:07:00 -0000 [thread overview]
Message-ID: <586512.99176.qm@web88311.mail.re4.yahoo.com> (raw)
In-Reply-To: <710C780E-6CF3-4950-9A39-8CFC26B08C2D@latencyzero.com>
Cygwin is ALWAYS well behind. But I have had no
problem building gcc 4.2.x using cygwin (I used gcc
3.4 to build gcc 4.2.1, and 4.2.1 to build 4.2.2).
If you need 4.2.x to do your cross build, you can
build it native first, and then do your cross build
(unless your cross compiler needs something not in
cygwin - I wouldn't know since I don't attempt
building a cross compiler). If you want, I can post
the configure parameters I used.
HTH
Ted
--- Rick Mann <rmann@latencyzero.com> wrote:
> I've been able to build an xscale-elf-targeted GCC
> (and binutils and
> newlib) on Mac OS X. Now I have to do the same thing
> on Cygwin (ugh),
> and it doesn't work.
>
> One thing is that Cygwin has GCC 3.4, not 4.x.
>
> Looking around, the GCC installation notes seem to
> imply that 3.4 can
> build 4.x, so I'm wondering if there's something in
> particular I need
> to watch out for?
>
> TIA,
> Rick
>
>
next prev parent reply other threads:[~2007-12-11 23:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 22:57 Rick Mann
2007-12-11 23:07 ` Ted Byers [this message]
2007-12-12 0:34 ` Brian Dessent
2007-12-12 2:23 ` Ted Byers
2007-12-12 2:07 ` Tim Prince
2007-12-12 22:32 ` Rick Mann
2007-12-12 23:04 ` Brian Dessent
2007-12-12 23:16 ` Rick Mann
2007-12-12 23:48 ` Brian Dessent
2007-12-13 0:02 ` Rick Mann
2007-12-13 0:06 ` Brian Dessent
2007-12-13 3:43 ` Rick Mann
2007-12-14 0:35 ` Rick Mann
2007-12-14 0:44 ` Brian Dessent
2007-12-14 0:57 ` Ted Byers
2007-12-14 2:35 ` Rick Mann
2007-12-16 19:34 ` Kai Ruottu
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=586512.99176.qm@web88311.mail.re4.yahoo.com \
--to=r.ted.byers@rogers.com \
--cc=gcc-help@gcc.gnu.org \
--cc=rmann@latencyzero.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).