[bug #57962] apparent regression involving PATH resolution

Follow-up Comment #8, bug #57962 (project make): Thank you Paul ___ Reply to this item at: ___ Message sent via Savannah https://savannah.gnu.org/

[bug #57914] abspath does resolve symlink

Follow-up Comment #8, bug #57914 (project make): Right... GNU make doesn't have any option to act like "pwd -L" does when it manages paths. The user could do that themselves in their makefile since they have access to "$(PWD)". Maybe not pretty, but something like this could work: labspath =

[bug #57914] abspath does resolve symlink

Follow-up Comment #7, bug #57914 (project make): Thank you all for your explanations. I think I now understand it correctly :) [comment #6 comment #6:] > Just as another proof that it's a feature of the shell: if you don't use the shell's built-in pwd command but instead use /bin/pwd, you'll

Re: [bug #57674] regression in make 4.3 with makefile from stdin

On Wed, 2020-04-01 at 14:14 +0200, Andreas Schwab wrote: > On Mär 31 2020, Paul D. Smith wrote: > > > In GNU make 4.3, for performance reasons we choose to use > > posix_spawn() if it's available on the system. posix_spawn() > > doesn't do any path search, so we do it ourselves and we don't have

Re: [bug #57674] regression in make 4.3 with makefile from stdin

On Mär 31 2020, Paul D. Smith wrote: > In GNU make 4.3, for performance reasons we choose to use posix_spawn() if > it's available on the system. posix_spawn() doesn't do any path search, so we > do it ourselves and we don't have this backup default PATH lookup that > execvp() does. There is

[bug #57674] GNU make doesn't use default path if PATH not set

Update of bug #57674 (project make): Status:None => Fixed Open/Closed:Open => Closed Fixed Release:None => SCM