[bug #66085] second run of "make" requires user interaction

[G. Branden Robinson]

Follow-up Comment #7, bug #66085 (group groff):


[comment #6 comment #6:]
> So the Makefile is using $HOME/bin/mv rather than the system's mv to move
files.  This still feels mildly buggy,

I'm not sure I agree--why _shouldn't_ a build use $PATH to resolve command
names?  Historically, this is what is done.

I was going to mention the case of locating _cc_(1), but that may be a near
counterexample, thanks to the _make_(1) `CC` variable and the ubiquity of
cross-compiling (relative to 1970s Unix).

I can't point you to any authoritative, but I suppose I've worked for decades
under the assumption that PATH is honored in a build scenario just like any
other, and if you don't like what the build finds in $PATH, do any of:

1.  Change $PATH when building.
2.  Use _make_ macros to override command selections (and carefully write your
Makefile rules to use those macros).
3.  Build in a chroot, container, or alternative user account with a cleaner
environment.

Just musing.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?66085>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

signature.asc
Description: PGP signature