[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Make CVS HEAD version build out of the box

From: Eli Zaretskii
Subject: Re: Make CVS HEAD version build out of the box
Date: Mon, 01 Oct 2007 18:24:25 +0200

> Date: Mon, 1 Oct 2007 22:36:41 +0800
> From: "Yongwei Wu" <address@hidden>
> Cc: address@hidden
> > 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.
> I checked config.h, and the only things I have some doubts are:

I didn't mean config.h, I meant specifically config.h.W32.template.
(Because you ran the configure script, it used the general
rather than the W32 template, to create config.h, and does
not have those symbols.)  There are several symbols near the end of
the template that you need to consider:


Please read the comments that describe each one of them (and the code
that uses them, if the comments are not clear enough).

> I also doubt config.h.W32.template may be a little out of date.  It
> defines some macros that are never used, like HAVE_LONG_FILE_NAMES and

I guess someone needs to resync the templates (not only W32) with

> I mean, which is the official position where I can grab the version
> number (instead of running autoreconf)?

I don't know.  Paul, can you help?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]