Quoting Eli Zaretskii <[EMAIL PROTECTED]>:
Date: Mon, 1 Oct 2007 13:12:41 +0800
From: "Yongwei Wu" <[EMAIL PROTECTED]>
Cc: make-w32@gnu.org
(Slapping myself) sorry for my folly. With your information I
successfully built Make under Cygwin:
autoreconf -i
./configure --build=i686-pc-mingw32 CC='gcc -mno-cygwin'
cd w32 && make && cd ..
make make.exe
Beware: the make.exe binary produced in this way is not guaranteed to
behave like intended. This is because this way of building a native
Windows port of Make is not officially supported. As one caveat, you
will see that config.h.W32.template has near its end a few symbols
whose definition changes Make's behavior wrt program invocation with
various shells you might have installed: I'm not sure what the
configure script does with those definitions, so please at least look
at those symbols and verify that the binary you produced will behave
as you'd like it to.
There should be no reason it shouldn't work but isn't --build the wrong
switch? Don't you want --host instead? The --build switch is saying
that your environment is i686-pc-mingw32 but your environment is cygwin.
I saw now the way my copying config.h.W32.template to config.h was not
correct. Do I have to manually replace %PACKAGE% and %VERSION%? Is
there an easy way?
Well, you could edit it with Sed, instead of just copying. Someone
who dares to build a CVS version can be expected to have Sed
installed.
I have a feeling that Yongwei knows what he is doing.
Earnie
_______________________________________________
Make-w32 mailing list
Make-w32@gnu.org
http://lists.gnu.org/mailman/listinfo/make-w32
