If so, could you please post it again, rebased on the current Git
There is an issue here: I noticed that when I was trying to build
(cross-compile) Make for Windows using a gcc + mingw-w64
cross-compiler (using Autotools, not build_w32.bat), there was a
big difference depending on whether I was using the Make source
code from git or the tarball.
When trying from git, which was my first attempt, I was getting
compilation warnings which were turning themselves into errors,
so I never managed to build.
When I used the sources extracted from the tarball though, this
simply wasn't the case so I was able to cross-compile just fine.
Then the problem was how to track my changes, since I don't
have git any more. What I did just to get a patch posted was
to simply 'git init' a repository in the extracted sources just so
I could use 'git diff' and so forth. That way, I created the patch
I originally posted.
The problem now is that in order to rebase on the current Git
master, I'd have to use Git, so I'll fall back to the original problem
of not being able to build because of the warnings being treated
Is this a known issue? Or is it just that not many people are
cross-compiling for Windows using gcc and autotools (i.e. not
That being said, I haven't tried to build the Git source code
using build_w32.bat, so for all I know maybe that doesn't
lead to the warnings/errors I got with autotools (mostly because
that would be a native compile, as opposed to the cross-compile
I am doing with autotools).
And would you please consider working on changing build_w32.bat as
Absolutely, I haven't forgotten about this. I haven't looked into
that file at all though, so I don't know how it configures its Makefiles,
how it detects the toolchain etc, so I may need some help to speed
things up. But definitely planning to do so in the coming days, or
weekend at worst.