public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin-talk@cygwin.com
Subject: -mno-cygwin, huh?, wha? [RE: Pbm with ar.h when compiling make-3.80 for mingw]
Date: Wed, 15 Feb 2006 19:26:00 -0000	[thread overview]
Message-ID: <20060215192647.GJ4169@trixie.casa.cgf.cx> (raw)

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.

cgf

----- Forwarded message from Dave Korn -----

From: Dave Korn
To: cygwin
Subject: RE: Pbm with ar.h when compiling make-3.80 for mingw
Date: Wed, 15 Feb 2006 18:50:42 -0000

On 15 February 2006 18:42, Xavier Marichal wrote:

> Hi!
> 
> To make a long story short, I want to re-build make-3.80 for mingw/msys
> usage because I encounter some problems with the mingw distribution...

  WTF does the mingw version of make have to with cygwin?

> After downloading the sources fro gnu, I launched ./configure.
> Then, in-line with the recommendations of
> http://www.delorie.com/howto/cygwin/mno-cygwin-howto.html, I did modify
> the resulting Makefile in the following way:
> CFLAGS = -g -O2 -mno-cygwin

  What part of "NO CYGWIN" don't you get?

> What shall I do then? 

  Talk to the MinGW hand^Wlist, because the cygwin face-aint-listening?

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

----- End forwarded message -----

             reply	other threads:[~2006-02-15 19:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15 19:26 Christopher Faylor [this message]
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

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=20060215192647.GJ4169@trixie.casa.cgf.cx \
    --to=cgf-no-personal-reply-please@cygwin.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).