From: Igor Peshansky <pechtcha@cs.nyu.edu>
To: The Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>
Subject: RE: -mno-cygwin, huh?, wha? [RE: Pbm with ar.h when compiling make-3.80 for mingw]
Date: Wed, 15 Feb 2006 23:50:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.63.0602151847140.21867@access1.cims.nyu.edu> (raw)
In-Reply-To: <000101c63268$b5b23320$a501a8c0@CAM.ARTIMI.COM>
On Wed, 15 Feb 2006, Dave Korn wrote:
> On 15 February 2006 19:35, Christopher Faylor wrote:
>
> > On Wed, Feb 15, 2006 at 07:31:38PM -0000, Dave Korn wrote:
> >> On 15 February 2006 19:27, Christopher Faylor wrote:
> >>> Thanks, Dave, for your continued vigilance.
> >>>
> >>> Is there something (besides hippos) in the water or something? We seem
> >>> to be getting an increased number of non-cygwin "problem reports"
> >>> recently.
> >>
> >> Yeh, I've noticed, the situation looks real bad.
> >>
> >> In fact you might even say it mings!
> >
> > I wonder if it would matters at all if we just got rid of the
> > -mno-cygwin option entirely. I don't mind making a mingw
> > "cross-compiler" part of the requirement for building cygwin and maybe
> > it would make the issue really clear.
>
> Nah, let's just hide it. Rename it
> "-mno-cygwin-but-i-would-like-a-hippo-please-and-can-i-have-that-with-cheese-to-go-and-by-the-way-i-really-promise-not-to-mail-the-cygwin-list-with-any-support-request-as-a-result-of-doing-whatever-it-is-i'm-doing-right-now".
Hippo steak, mmm-mmm... BTW, I can just *see* people popping up with
complaints about how this completely breaks their nmake build files due to
command line length limitations...
Seriously, though -- why not simply rename it in some way that makes it
clear this is a MinGW cross-compiler? Something like "-mcross-mingw32",
or even make it "--target=i686-pc-mingw32"?
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"
prev parent reply other threads:[~2006-02-15 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 19:26 Christopher Faylor
2006-02-15 19:31 ` Dave Korn
2006-02-15 19:35 ` Christopher Faylor
2006-02-15 19:49 ` Dave Korn
2006-02-15 23:50 ` Igor Peshansky [this message]
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=Pine.GSO.4.63.0602151847140.21867@access1.cims.nyu.edu \
--to=pechtcha@cs.nyu.edu \
--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).