[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: wrong link command called
From: |
Alessandro Vesely |
Subject: |
Re: wrong link command called |
Date: |
Thu, 31 Mar 2005 10:00:32 +0200 |
"Paul D. Smith" wrote:
>
> I added a note to that bug.
> [http://savannah.gnu.org/bugs/?func=detailitem&item_id=7201]
>
Paul's point is correct: since unixy shells do try and subvert
the OS native behaviour, when make uses them it should disable
the "fast path" or mimic the unixy shells.
I would suggest disabling the fast path, for a couple of reasons.
1. MinGW and Cygwin shells may have to apply unusual workarounds in
order to be consistent. Trying to mimic them is aiming at a moving
target.
2. make mimics the Windows' native shells (command.com, cmd.exe)
quite well. Actually, the fast path works better than the slow one
in this case: That's because Windows' native shells don't accept
forward slashes, therefore commands whose executables contain an
explicit path only work if they will take the fast path or if the
user does $(subst /,\,$(explicit_path)) -that includes commands
using $(MAKE).
- Re: wrong link command called, (continued)
- Re: wrong link command called, Earnie Boyd, 2005/03/29
- RE: wrong link command called, Jonathan Baccash, 2005/03/29
- RE: wrong link command called, Jonathan Baccash, 2005/03/29
- RE: wrong link command called, Jonathan Baccash, 2005/03/29
- RE: wrong link command called, Jonathan Baccash, 2005/03/30
- RE: wrong link command called, Ian Dunbar, 2005/03/30