public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Paul D. Smith" <psmith@gnu.org>
To: help-gcc@gnu.org
Subject: Re: dmake, GNU make, gcc, and auto-dependencies
Date: Mon, 06 Dec 1999 20:31:00 -0000	[thread overview]
Message-ID: <p5yab78jif.fsf@baynetworks.com> (raw)
In-Reply-To: <384c5525.431857552@news.mul.nec.com.au>

%% stuarts@icpdd.neca.nec.com.au (Stuart Summerville) writes:

  >> ', needed by `fred'.  Stop.arget `

  ss> Goddam!! just happened to load the makefile into a unix editor (as
  ss> opposed to the win32 one I normally use) & saw the CR on the end
  ss> of the first line.  Removing it obviously fixed the problem.

Darn, and I knew that one, too :)

Whenever you see screwed up text like that you can always bet there's an
extraneous CR character in there resetting to the beginning of the line.

Anyway, if you upgrade to the latest GNU make (3.78.1) you won't have
this problem; it silently ignores CR's as part of CRNL pairs.

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <psmith@gnu.org>          Find some GNU make tips at:
 http://www.gnu.org                      http://www.ultranet.com/~pauld/gmake/
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist

WARNING: multiple messages have this Message-ID
From: "Paul D. Smith" <psmith@gnu.org>
To: help-gcc@gnu.org
Subject: Re: dmake, GNU make, gcc, and auto-dependencies
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <p5yab78jif.fsf@baynetworks.com> (raw)
Message-ID: <19991231222400.XZRQSxn4A5jJRT7JeG2Rqhi6F3KzRQyFxG6IYN_G-D4@z> (raw)
In-Reply-To: <384c5525.431857552@news.mul.nec.com.au>

%% stuarts@icpdd.neca.nec.com.au (Stuart Summerville) writes:

  >> ', needed by `fred'.  Stop.arget `

  ss> Goddam!! just happened to load the makefile into a unix editor (as
  ss> opposed to the win32 one I normally use) & saw the CR on the end
  ss> of the first line.  Removing it obviously fixed the problem.

Darn, and I knew that one, too :)

Whenever you see screwed up text like that you can always bet there's an
extraneous CR character in there resetting to the beginning of the line.

Anyway, if you upgrade to the latest GNU make (3.78.1) you won't have
this problem; it silently ignores CR's as part of CRNL pairs.

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <psmith@gnu.org>          Find some GNU make tips at:
 http://www.gnu.org                      http://www.ultranet.com/~pauld/gmake/
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist

  reply	other threads:[~1999-12-06 20:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-06  4:43 Stuart Summerville
1999-12-06  7:19 ` Paul D. Smith
1999-12-06 16:28   ` Stuart Summerville
1999-12-06 16:37     ` Stuart Summerville
1999-12-06 20:31       ` Paul D. Smith [this message]
1999-12-31 22:24         ` Paul D. Smith
1999-12-31 22:24       ` Stuart Summerville
1999-12-31 22:24     ` Stuart Summerville
1999-12-31 22:24   ` Paul D. Smith
1999-12-31 22:24 ` Stuart Summerville

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=p5yab78jif.fsf@baynetworks.com \
    --to=psmith@gnu.org \
    --cc=help-gcc@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).