From: "Stuart Yoder" <syoder@chicorysystems.com>
To: <cygwin@sourceware.cygnus.com>
Subject: make problem
Date: Thu, 01 Jun 2000 06:31:00 -0000 [thread overview]
Message-ID: <006601bfcbce$6010abb0$6f01a8c0@latte> (raw)
I've been using an installation of cygwin (cygwin20.1b) without
problems. make command is version 3.75.
I recently downloaded the most recent cygwin binaries including
make (version 3.77) and now make fails with any makefile
containing carriage return and line feeds. If I delete the carriage
returns from the makefile it works fine.
Am I missing some kind of setup parameter?
I've tried both unix and win32 for MAKE_MODE.
Stuart
syoder@chicorysystems.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-06-01 6:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-01 6:31 Stuart Yoder [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-16 9:28 Make Problem Deepa Mahajan
2006-03-16 15:27 ` Dave Korn
2000-06-01 6:39 make problem Earnie Boyd
[not found] <200002280744.XAA10334@shell.tsoft.com>
2000-02-29 10:14 ` Make problem Claire Hand
2000-02-29 10:14 ` Charlie Hand
[not found] ` <200002291816.NAA15176@smtp.mathworks.com>
2000-02-29 11:54 ` Paul Kinnucan
2000-02-29 14:17 ` Charlie Hand
[not found] ` <200002292217.OAA03331@cygnus.com>
2000-02-29 14:33 ` Chris Faylor
2000-02-27 23:44 Charlie Hand
1999-03-14 9:22 make Problem David M. Drukker
[not found] ` < 3.0.5.32.19990314113425.0086a2b0@eco.utexas.edu >
1999-03-14 9:59 ` Mumit Khan
1999-03-31 19:45 ` Mumit Khan
1999-03-31 19:45 ` David M. Drukker
1999-03-07 23:11 Make problem Joost Kraaijeveld
1999-03-31 19:45 ` Joost Kraaijeveld
1998-01-24 14:35 MAKE Problem naftali kirsh
1997-12-29 1:37 make problem Ivo Abeloos
1997-10-06 19:07 Yang Shuqiang
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='006601bfcbce$6010abb0$6f01a8c0@latte' \
--to=syoder@chicorysystems.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).