[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RFC: Does hand editing of "config.h" make sense?
|
From: |
Keith MARSHALL |
|
Subject: |
Re: RFC: Does hand editing of "config.h" make sense? |
|
Date: |
Fri, 27 May 2005 16:14:59 +0100 |
Bob Friesenhahn wrote, quoting me:
>> BTW, why does the "#undef HAVE_SOMEHEADER_H" in config.h.in get
>> wrapped in comment marks, when it is copied into config.h? Does it
>> not make more sense to forcibly ensure that HAVE_SOMEHEADER_H is not
>> defined, if configure has determined that someheader.h isn't present?
>> Or, do some [broken] compilers choke on "#undef AN_UNDEFINED_SYMBOL"?
>
> The explanation for this is simple. If the user wants to manually
> define the value (e.g. via configure CPPFLAGS argument) she can do so
> without the problem that the value set is immediately unset again by
> config.h.
Yes, I see the logic of that. But, if configure has already determined
that the header file is not present, or at least not usable, why would
any user realistically want to do that?
Best regards,
Keith.