So here is what I did. I installed msys2 using the directions at
http://msys2.github.io/
My msys2 does not have a make.exe. My c:/mingw64/bin does have a make
called *mingw32-make.exe*
I renamed that to make64 and then in msys2 console I did the following
*export PATH=/c/mingw64/bin:$PATH*
as a result of this I have a make64.exe available.
On Mon, May 11, 2015 at 2:54 PM, David Macek <[email protected]>
wrote:
> Please use the Reply All feature of your mail client, so that your
> messages make it to the mailing list (instead of just me).
>
> On 11. 5. 2015 23:27, James Franco wrote:
> > I tried creating a makefile with a simple "Hello World" and it works. So
> I am not sure what the problem might be.
>
> That's weird. I can't think of any reasonably testable hypotheses about
> what's wrong.
>
> I noticed though, that you're using some "make64" for your build. I used
> regular make from MSYS2. Could that be the source of the problem?
>
> > However I did notice something when building with msys (instead of msys2)
> > I get the following output *chmod a+rx libACE.dll * and the ebuild
> continues. Normally in msys2 instead of *chmod a+rx libACE.dll *message I
> would get the error message that I have been complaining about.
>
> This is expected. The chmod command is most likely the next command in the
> build, but the error stops the build, so the chmod command is never
> executed.
>
> --
> David Macek
>
>
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Msys2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/msys2-users
