[Mingw-notify] [ mingw-Support Requests-1631258 ] CreateProcess() in make.exe interacts badly with MS link.exe

[SourceForge.net <no...@so...>]

Support Requests item #1631258, was opened at 2007-01-09 03:51
Message generated for change (Comment added) made by earnie
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=202435&aid=1631258&group_id=2435

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Pending
Priority: 5
Private: No
Submitted By: Marek T (marektel)
Assigned to: Earnie Boyd (earnie)
Summary: CreateProcess() in make.exe interacts badly with MS link.exe

Initial Comment:
Hello,

Just installed mingw make.exe and the two requisite DLLs such that I could compile a MS VC++ project using GNU make. Everything is fine until it tries to link, at which point, 'make -d' returns the following (relevant) information:

link /nologo /subsystem:console /incremental:no /nodefaultlib:libcd /out:gapexe.exe rdtsc_time.obj gapexe.obj libconf.lib
CreateProcess(C:\Program Files\Microsoft Visual Studio .NET 2003\VC7\BIN\link.exe,link /nologo /subsystem:console /incremental:no /nodefaultlib:libcd /out:gapexe.exe rdtsc_time.obj gapexe.obj libconf.lib,...)

...

LINK : fatal error LNK1181: cannot open input file 'link.obj'

Close examination of the CreateProcess() debug line, it seems that the linker interprets the 'link' as 'link.obj' in the 2nd param and tries to find the file. When it cannot, it fails. This is with the latest version of MingW32 make, that is, ver 3.81-1.

My workaround hack includes adding a valid link.obj file in the directory where I link, at which point it works, but I thought someone should know about this.

Thanks,
Marek


----------------------------------------------------------------------

>Comment By: Earnie Boyd (earnie)
Date: 2007-01-12 08:23

Message:
Logged In: YES 
user_id=15438
Originator: NO

I suggest that you take your issue to mak...@gn....  Perhaps someone
with more knowledge of the inner workings of the windows port can help.  It
appears that perhaps the spaces in the path to link.exe is perhaps an issue
based on your CreateProcess output.

----------------------------------------------------------------------

Comment By: Marek T (marektel)
Date: 2007-01-11 21:37

Message:
Logged In: YES 
user_id=1687182
Originator: YES

Hello,

Apologies for mis-categorizing the report. Version:

C:\> make --version
GNU Make 3.81
Copyright (C) 2006  Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

This program built for i686-pc-mingw32

Thanks again,
Marek


----------------------------------------------------------------------

Comment By: Earnie Boyd (earnie)
Date: 2007-01-09 08:23

Message:
Logged In: YES 
user_id=15438
Originator: NO

Link is not a binutils binary.

Which version of make are you using; i.e. what is the output of ``make
--version''?

This appears to be an environment issue.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=202435&aid=1631258&group_id=2435