From: "Brown, Kim" <Kim.Brown@wl.com>
To: cygwin@sourceware.cygnus.com
Subject: RE: Problem with make
Date: Thu, 10 Jun 1999 04:56:00 -0000 [thread overview]
Message-ID: <9F481A71957AD111BB2300805FE65D2504749D35@mpisex02.mops.wl.com> (raw)
My version of GNU make is 3.75 (supplied with b20.1 I think). I did not
know there was a 3.77 out there. Looks like I need to upgrade and see if my
problems with makefiles go away.
> -----Original Message-----
> From: N8TM@aol.com [ mailto:N8TM@aol.com ]
> Sent: Thursday, June 10, 1999 2:12 AM
> To: Kim.Brown@wl.com; Dave.Blob@gs.com; cygwin@sourceware.cygnus.com
> Subject: Re: Problem with make
>
>
> In a message dated 6/9/99 9:45:12 AM Pacific Daylight Time,
> Kim.Brown@wl.com
> writes:
>
> > I have found GNU make to be buggy with some makefiles,
> especially those
> > generated by PERL install packages. I just use nmake from
> microsoft
> without
> > problems. Anyone else have problems with GNU make?
>
> Do you mean gnu make as in b20.1? It has serious problems
> with recursive
> makefiles (e.g. egcs configure and build). For my purposes,
> replacing it
> with make-3.77 has been satisfactory,
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: "Brown, Kim" <Kim.Brown@wl.com>
To: cygwin@sourceware.cygnus.com
Subject: RE: Problem with make
Date: Wed, 30 Jun 1999 22:10:00 -0000 [thread overview]
Message-ID: <9F481A71957AD111BB2300805FE65D2504749D35@mpisex02.mops.wl.com> (raw)
Message-ID: <19990630221000.XUfo6cvrKpDevFSpmZVDUmMTC8FgtdsG-kQJrdzETQk@z> (raw)
My version of GNU make is 3.75 (supplied with b20.1 I think). I did not
know there was a 3.77 out there. Looks like I need to upgrade and see if my
problems with makefiles go away.
> -----Original Message-----
> From: N8TM@aol.com [ mailto:N8TM@aol.com ]
> Sent: Thursday, June 10, 1999 2:12 AM
> To: Kim.Brown@wl.com; Dave.Blob@gs.com; cygwin@sourceware.cygnus.com
> Subject: Re: Problem with make
>
>
> In a message dated 6/9/99 9:45:12 AM Pacific Daylight Time,
> Kim.Brown@wl.com
> writes:
>
> > I have found GNU make to be buggy with some makefiles,
> especially those
> > generated by PERL install packages. I just use nmake from
> microsoft
> without
> > problems. Anyone else have problems with GNU make?
>
> Do you mean gnu make as in b20.1? It has serious problems
> with recursive
> makefiles (e.g. egcs configure and build). For my purposes,
> replacing it
> with make-3.77 has been satisfactory,
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-06-10 4:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-10 4:56 Brown, Kim [this message]
1999-06-30 22:10 ` Brown, Kim
-- strict thread matches above, loose matches on Subject: below --
2013-06-05 7:00 Lange, Jan-Erik
2013-06-05 7:31 ` Corinna Vinschen
2002-04-22 0:50 problem " Jason Morgan
[not found] <009001c17d8a$9ad87380$9a5f07d5@BRAMSCHE>
2001-12-05 5:26 ` Earnie Boyd
[not found] <200103150254.SAA09865@cygnus.com>
2001-03-14 19:04 ` Problem " Christopher Faylor
2001-03-14 18:54 Mark Paulus
2000-08-17 9:43 problem " Brian Pollard
2000-08-17 23:26 ` Lassi A. Tuura
2000-08-16 15:58 Noel L Yap
2000-08-16 15:23 Noel L Yap
2000-08-16 13:12 Heribert Dahms
2000-08-16 23:01 ` Lassi A. Tuura
2000-08-15 10:37 Brian Pollard
2000-08-16 0:01 ` Avraham H. Fraenkel
2000-08-16 4:34 ` Lassi A. Tuura
1999-06-09 23:12 Problem " N8TM
1999-06-30 22:10 ` N8TM
1999-06-09 12:17 Phil Edwards
1999-06-30 22:10 ` Phil Edwards
1999-06-09 9:43 Brown, Kim
1999-06-09 12:26 ` Don Sharp
1999-06-30 22:10 ` Don Sharp
1999-06-30 22:10 ` Brown, Kim
1999-06-09 9:36 Blob, Dave
1999-06-30 22:10 ` Blob, Dave
1998-08-06 14:36 problem " Stuart
1998-08-07 10:39 ` Stuart
1998-08-09 11:19 ` Pete Jordan
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=9F481A71957AD111BB2300805FE65D2504749D35@mpisex02.mops.wl.com \
--to=kim.brown@wl.com \
--cc=cygwin@sourceware.cygnus.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).