[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Build with cygwin gcc
From: |
Stacy Leon |
Subject: |
Re: Build with cygwin gcc |
Date: |
Mon, 4 Jun 2012 10:48:53 -0700 (PDT) |
OK Good enough. Thanks. I guess wonder how they produce the prepackaged
cygwin make. When I use "their" prepackaged make it cannot handle drive
letters at all.
Eli Zaretskii wrote:
>
>> Date: Mon, 4 Jun 2012 09:40:12 -0700 (PDT)
>> From: Stacy Leon <address@hidden>
>>
>> Just to clarify, I am not talking about using cygwin make, where they
>> completely disable using drive letters. I am just talking about using the
>> standard make 3.82 source and build with cygwin gcc.
>
> When you use the standard Make sources, and configure and build with
> Cygwin GCC, you get the Cygwin Make. You should see that by typing
> "make --version", it shows its target on the 2nd line. That one that
> is built for native tools says this:
>
> Built for i686-pc-mingw32
>
>> All of my microsoft compiled code builds fine when using the
>> resultant make.exe.
>
> They mostly will. The problems are subtle, and if you are lucky, you
> will never see them. But they are there nonetheless.
>
>> I am not using
>> the w32 directory at all, while it seems all other builds require it.
>
> One more sign that you've got a Cygwin Make.
>
> _______________________________________________
> Make-w32 mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/make-w32
>
>
--
View this message in context:
http://old.nabble.com/Build-with-cygwin-gcc-tp33958406p33959472.html
Sent from the Gnu - Make - W32 mailing list archive at Nabble.com.