Web lists-archives.org

Re: [Mingw-users] Possible problem with mingw32-make-3.81-20080326.tar.gz

Quoting Greg Chicares <gchicares@xxxxxxxxxxxxx>:

> On 2008-04-13 00:43Z, Bob wrote:
>> Greg Chicares <gchicares@...> writes:
>>
> [...add 'C:\msys\1.0\bin' to PATH and invoke 'mingw32-make'...]

I recommend that this not be done at the registry but after starting a 
command window.  It avoids issues with duplicity of the MSYS DLL or 
problems when the CYGWIN DLL resides on the same server.  In the case 
of duplicity, if the user installs a package containing a copy of MSYS 
it will work OOB if the user does not have a C:\msys\1.0\bin it the 
PATH.  Otherwise the user will run into problems with the other package.

>>
>>> Instead of doing that, why don't you just use MSYS's own 'make'?
>>
>> I had thought that the mingw32 make was the "preferred" binary to use
>
> It seems that there's some confusion, and I figure this is the
> right place to ask for authoritative guidance.
>

Authoritative answer:
MSYS' make is to be used within the environment provided by MSYS.  
MSYS' make is provided because the native (uses the MSVCRT runtime) 
mingw32-make doesn't execute properly within the MSYS shell.  Had I had 
success with using the native version of make within MSYS' shell then 
there would be no need to have another copy.

Mingw32-make however can use the MSYS shell without problems.  I.E.: 
Invoking the MSYS shell from within the native make works as expected.

Earnie

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
MinGW-users mailing list
MinGW-users@xxxxxxxxxxxxxxxxxxxxx

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users