[Top][All Lists]

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

Re: Some questions about MAKE_HOST and LDFLAGS

From: Eli Zaretskii
Subject: Re: Some questions about MAKE_HOST and LDFLAGS
Date: Sat, 02 Jul 2005 13:26:50 +0200

[Fair warning: I'm not the official maintainer of GNU Make.]

> From: =?iso-8859-1?Q?Jerker_B=E4ck?= <address@hidden>
> Date: Sat, 2 Jul 2005 09:30:04 +0200
> There's a string constant in config.h named MAKE_HOST
> #define MAKE_HOST "Windows32" or "i686-pc-cygwin" ...
> In the make code this is used only in version string output.
> Does it matter what this string says?
> Is it extracted by some tool (ie autoconfig) and used somehow?

It is computed by the configure script (by invoking `uname'), and
displayed by the --help and --version command-line options.

> What is the proper way to force inclusion of a library?

LDFLAGS is it.

> autoconfig and configure often test the compiler by compile a small program.
> This program is linked to libc.lib. However, this is not enough for later
> versions of the Microsoft C runtime library. You need at least one more
> linked library (ie BufferOverflowU.lib) => linker failure.

Why does one need to link against BufferOverflowU.lib?  If it is
always required for Cygwin, the proper fix would be to have the
configure script do that automatically when Make is built on Cygwin.

reply via email to

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