All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henning Makholm <henning@makholm.net>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: henning@makholm.net, bug-make@gnu.org,
	linux-hams@vger.kernel.org, linux-kernel@vger.kernel.org,
	sailer@ife.ee.ethz.ch
Subject: Re: make-3.79.1 bug breaks linux-2.5.24/drivers/net/hamradio/soundmodem
Date: 24 Jun 2002 14:13:10 +0200	[thread overview]
Message-ID: <yahn0tklvs9.fsf@pc-043.diku.dk> (raw)
In-Reply-To: "Adam J. Richter"'s message of "Sat, 22 Jun 2002 14:56:23 -0700"

Scripsit "Adam J. Richter" <adam@yggdrasil.com>

> >I'm not sure this is really a bug either. It is a Good Thing that make
> >tries to normalize the names of targets and dependencies internally,
> >lest the build may be incomplete or redundant if make does not realize
> >that foo.bar and ./foo.bar is the same file. It is quite reasonable
> >for $< to unfold to the *canonical* name of the file in question, I
> >think.

> 	That just makes the behavior of make less predictable.
> Whatever make does with the file names internally is its own business.
> Rewriting the file names passed to commands unnecessarily is
> potentially a big problem.

It is not rewriting file names. It is just substituting the name of
the dependency for the $< variable, just as documented.

> >If one absolutely wants the command to use the exact form of the
> >dependency that's used in the dependency list, it's easy to simply
> >reproduce that form, replacing the % by $*

> 	Sorry, I do not understand what you mean.

It wasn't right anyway. I remembered the semantics of $* when the file
name contains slashes wrong.

-- 
Henning Makholm                      "They are trying to prove a hypothesis,
                             they are down here gathering data every season,
                       they're publishing results in peer-reviewed journals.
                     They're wrong, I think, but they are still scientists."

  reply	other threads:[~2002-06-24 12:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-22 21:56 make-3.79.1 bug breaks linux-2.5.24/drivers/net/hamradio/soundmodem Adam J. Richter
2002-06-24 12:13 ` Henning Makholm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-22  6:57 Adam J. Richter
2002-06-22 13:51 ` Henning Makholm
2002-06-22 20:23   ` Riley Williams
2002-06-22 21:24     ` Kai Germaschewski
2002-06-22 21:24       ` Kai Germaschewski
2002-06-22 23:01       ` Riley Williams
2002-06-24 12:07         ` Henning Makholm
2002-06-25  4:23         ` Paul D. Smith
2002-06-24 12:00     ` Henning Makholm

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=yahn0tklvs9.fsf@pc-043.diku.dk \
    --to=henning@makholm.net \
    --cc=adam@yggdrasil.com \
    --cc=bug-make@gnu.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sailer@ife.ee.ethz.ch \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.