[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: wrong link command called

From: Earnie Boyd
Subject: Re: wrong link command called
Date: Tue, 29 Mar 2005 06:47:59 -0500 (EST)
User-agent: SquirrelMail/1.4.3a

<quote who="Jonathan Baccash">
> Try `link --help' for more information.
> C:\cygwin\bin\make.exe: *** [my.exe] Error 256
> From my command shell, I try "which link" and I get
> /cygdrive/c/PF/MSVS2003/VC7/BIN/link, which is correct.  But there is
> another link program in C:/cygwin/bin, which is also where I have put
> make.exe, and this other link does something completely different.  The
> problem occurs in sub_proc.c line 330 the call to OpenFile().  According
> to MSDN library
> base/openfile.asp, the call looks in the directory where the application
> was loaded even before looking in PATH.  This is extremely weird,
> because if I change the command to require invocation of the shell, i.e.
> "which link && link /DEBUG $^ /OUT:$@", makefile works as intended.

If you set and export PATH from within the Makefile does it help/

> Is this a known issue?  Is this a bug, or is this the intended behavior?
> I'm wondering why make doesn't just always execute the shell?
> Performance?  This might be difficult to fix otherwise - is the order of
> lookup for cmd.exe the same as for OpenFile?

It is dependent upon the environment in which you operate.  Your issue is
not make specific it is environment specific.  You may need to change the
Windows value of PATH in order to have the fact that you have
/cygwin/bin/link and /cygdrive/c/PF/MSVS2003/VC7/BIN/link in PATH.  You
could try renaming /cygwin/bin/link I'm not sure what package that comes
from but some invocation of setup update may cause it to be reinstated.


      MinGW -
       Wiki -
 SF Project -
Job Listing -

reply via email to

[Prev in Thread] Current Thread [Next in Thread]