[bug #42690] make unconditionally resolves the current directory

2014-07-05 Thread anonymous 
URL:
  

 Summary: make unconditionally resolves the current directory
 Project: make
Submitted by: None
Submitted on: Sat 05 Jul 2014 07:57:46 PM UTC
Severity: 3 - Normal
  Item Group: None
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
   Component Version: None
Operating System: None
   Fixed Release: None
   Triage Status: None

___

Details:

{ cd /tmp && mkdir a && ln -sT a b && cd b && make -w; }

make: Entering directory `/tmp/a'

Why not /tmp/b?  Is there an option to prevent this resolution?
I understand that relative path names must be resolved; 
but could you leave directory aliases as they are please?

This hit me when I tried to make in a directory that had a colon in the name;

this caused targets containing $(CURDIR) to be split and resulted in an
error;
I made a symbolic link to avoid the path with colon but it did not work;
make decided it would rather use the original path instead.

And, last but not least, this behaviour is undocumented 
(at least in the info file).





___

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

[bug #42690] make unconditionally resolves the current directory

2014-07-05 Thread Christopher Yeleighton 
Follow-up Comment #1, bug #42690 (project make):




 


___

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: [bug #42690] make unconditionally resolves the current directory

2014-07-05 Thread Philip Guenther 
On Sat, Jul 5, 2014 at 12:57 PM, anonymous  wrote:

> { cd /tmp && mkdir a && ln -sT a b && cd b && make -w; }
>
> make: Entering directory `/tmp/a'
>
> Why not /tmp/b?  Is there an option to prevent this resolution?
> I understand that relative path names must be resolved;
> but could you leave directory aliases as they are please?
>

The best make would be able to do would be to model its behavior on that of
"pwd -L": if the PWD environment variable is set to an absolute path with
no ".." or "." components that resolves to the process's current directory,
then use that instead of the path from getcwd().


This hit me when I tried to make in a directory that had a colon in the
> name;
>

Doctor says: "Don't do that!"   make is only one of many program which you
will have problems with.


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