[bug #42690] make unconditionally resolves the current directory

[Paul D. Smith]

Update of bug #42690 (project make):

  Status:None => Not A Bug  
 Open/Closed:Open => Closed 

___

Follow-up Comment #2:

The problem is make cannot find out what the path you used was.  Before make
is started, the "cd" will resolve the symbolic link and when make starts and
determines what its working directory is, that directory will be the final
destination.  Symbolic links are one-way: there is no way to "go back" through
the link.  Programs cannot tell how you got to the working directory, they
only know where there are now and they only know the real path of that
directory.

Only the parent shell, where the "cd" ran, can know that you used a symbolic
link to get where you are, rather than the "real" path.  Some shells will set
an environment variable, like "PWD", that contains the "virtual" path.  Some
do not.  Sometimes that variable will be exported so that programs like make
can see it.  Other times not.  It's not reliable, so make does not use it. 
However, if your shell does support this then you can use it yourself since
all environment variables are imported into make as make variables.  Of course
if someone uses your makefile and they do not use a shell that supports this,
then they won't be able to take advantage of it.

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/


___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make

Re: Add "makefile.mak" to list of default makefiles

[Paul Smith]

On Mon, 2014-06-30 at 21:28 +0100, Jonny Grant wrote:
> I have a few, but triggered by make -f makefile.mak. So it would be
> quite useful GNU Make could pick up the Windows makefile extension
> .MAK

If Eli feels this is useful for Windows implementations he can add it;
however, I don't want this added for the non-Windows ports.  I've never
seen anyone name a makefile like this on any UNIX/POSIX system, ever.

As Reinier points out, on UNIX/POSIX systems you often see ".mk" used as
an extension, but never (IME) "Makefile.mk"; UNIX/POSIX environments
don't rely (solely) on extensions and (again IME) have no problem
understanding that files named "Makefile" or "makefile" are makefiles,
even without extensions.

Renaming the Windows README files is also fine with me if it's fine with
Eli.


___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make

[bug #41983] $(file) function crashes make

[Paul D. Smith]

Update of bug #41983 (project make):

  Status:None => Fixed  
 Assigned to:None => psmith 
 Open/Closed:Open => Closed 
Operating System:None => Any
   Fixed Release:None => SCM
   Triage Status:None => Small Effort   

___

Follow-up Comment #5:

I pushed a fix for this as described below.

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/


___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make