Re: [RFC] Correctly handling MinGW-w64

["Óscar Fuentes" <ofv@wanadoo.es>]

Paul Eggert <eggert@cs.ucla.edu> writes:

> Óscar Fuentes wrote:
>> I thought that this type of tasks are the raison d'être of `configure'.
>
> No, the point of 'configure' is to do things that ordinary C and
> 'make' cannot. Here, we have something that ordinary C can do, so
> 'configure' isn't needed.

Ok.

>> Doing that is a kludge.
>
> Perhaps, but doing it in 'configure' is a worse kludge.  The stuff in
> 'conf_post.h' is, by design, included everywhere, and it's the logical
> place to put global things that don't need 'configure''s help.

After looking at it, seems that 'conf_post.h' can do the job. But
instead of placing the #define on some header that 'conf_post.h'
includes, I'll like to put it in 'conf_post.h' itself. There are similar
chunks of code there, so I guess that there is no problem.

> More generally, it would be better yet
[snip]

Indeed.