On Tue, 18 Sep 2012, Peter Rosin wrote:
There is no evidence that modern m4 does not build properly on MSYS, which
is what is interesting. A MinGW-m4 is not all that interesting in the
autotools context. What Bob tried (a MinGW-m4) was simply wrong, but the
reason for the attempt was surely because he had no tools to build MSYS
binaries installed. Very few do, and I suspect that most that do have them
installed don't know exactly what they're doing...
Right. My MinGW install is a random MinGW64 build that I installed
and passed my testing so that I what I am currently using. I could
search for a more recent MinGW64 build which might include a newer m4.
I did not see any MSYS development capacity in the MinGW64 I
downloaded and did not have time to research how to obtain it. Time
is short so I tend to cut corners.
Bob wrote this:
"Please make it so that it is possible to use a source tree
which has a .hg directory even if there is no 'git' program
available and even if autotools are not the exact same
version used to bootstrap the tree."
Assuming he meant a .git directory, this is something I need for my
workflow and something which has worked, so it is a regression. I'm
not sure if I want to --skip-git in my bootstrap, because then the
Cygwin side of things are not "as usual".
Right. I meant .git. :-)
It used to be possible to run the libtool test suite in a MSYS shell
using a CIFS mount of the same source tree that I use for my Unix type
systems. I used to do that on a periodic basis. Since the bootstrap
improvements, this does not seem to be possible. Perhaps I might
encounter a MSYS install which includes the newer m4 and a workable
'git'.
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________
https://lists.gnu.org/mailman/listinfo/libtool
