From: Eric Blake <eblake@redhat.com>
To: cygwin-talk@cygwin.com
Subject: Re: crossbuild cygwin-1.7.6-1 on linux x64
Date: Wed, 25 Aug 2010 21:31:00 -0000 [thread overview]
Message-ID: <4C758B94.4050802@redhat.com> (raw)
In-Reply-To: <4C7587AF.5010401@cygwin.com>
On 08/25/2010 03:14 PM, Larry Hall (Cygwin Developers) wrote:
>> I must now have genetic knowledge of building cross-compilers because
>> I don't see why everyone thinks this is such a big deal, requiring so
>> much discussion.
>
> cgf - the cross-compiler compiler. ;-)
Or, in the WJM vein,
the cross cross-compiler compiler :)
--
Eric Blake eblake@redhat.com +1-801-349-2682
Libvirt virtualization library http://libvirt.org
next parent reply other threads:[~2010-08-25 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1282736792.3228.ezmlm@cygwin.com>
[not found] ` <4C758389.9080608@cwilson.fastmail.fm>
[not found] ` <20100825211116.GB16178@ednor.casa.cgf.cx>
[not found] ` <4C7587AF.5010401@cygwin.com>
2010-08-25 21:31 ` Eric Blake [this message]
2010-08-26 5:44 ` Christopher Faylor
2010-09-02 23:52 ` Dave Korn
2010-09-03 7:49 ` Corinna Vinschen
2010-09-03 12:52 ` Chris Sutcliffe
2010-09-03 13:06 ` Buchbinder, Barry (NIH/NIAID) [E]
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=4C758B94.4050802@redhat.com \
--to=eblake@redhat.com \
--cc=cygwin-talk@cygwin.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).