From: Jim Northrup <glamdring-inc@comcast.net>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Gentoo/Cygwin?
Date: Thu, 24 Feb 2005 09:41:40 -0800 [thread overview]
Message-ID: <421E11D4.7060607@comcast.net> (raw)
In-Reply-To: <20050222171445.GA22112@curie-int.vc.shawcable.net>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
># file q821982.exe # it's a microsoft patch I had lying around
>q821982.exe: MS-DOS executable (EXE), OS/2 or MS Windows
># objdump -f q821982.exe
>q821982.exe: file format efi-app-ia32
>architecture: i386, flags 0x0000010a:
>EXEC_P, HAS_DEBUG, D_PAGED
>
>efi-app-ia32 is on your BFD target list, so by logical inverse of your
>statement, we do have business trying to support it.
>
>However I will concur that until there is sufficent demand (and I agree this is
>very hard to measure), getting Gentoo/Cygwin added to the tree probably won't
>happen.
>
for those who like cygwin and gentoo but are not reading gentoo-dev,
there is likely no demand.
even though I don't have a windows machine, I'm salivating at the thought.
[-- Attachment #2: glamdring-inc.vcf --]
[-- Type: text/x-vcard, Size: 175 bytes --]
begin:vcard
fn:James Northrup
n:Northrup;James
email;internet:glamdring-inc@comcast.net
tel;home:510 725 4587
tel;cell:408 896 6239
x-mozilla-html:TRUE
version:2.1
end:vcard
next prev parent reply other threads:[~2005-02-24 17:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 23:30 [gentoo-dev] Gentoo/Cygwin? Ciaran McCreesh
2005-02-21 23:42 ` Ioannis Aslanidis
2005-02-22 2:01 ` Patrick Dawson
2005-02-22 9:13 ` tchiwam
2005-02-22 12:39 ` Patrick Lauer
2005-02-22 15:33 ` M. Edward (Ed) Borasky
2005-02-22 12:32 ` Patrick Lauer
2005-02-22 16:44 ` Ned Ludd
2005-02-22 17:14 ` Robin H. Johnson
2005-02-24 17:41 ` Jim Northrup [this message]
2005-02-22 3:42 ` M. Edward (Ed) Borasky
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=421E11D4.7060607@comcast.net \
--to=glamdring-inc@comcast.net \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.gentoo.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