On 19 August 2015 at 14:53, Patrice Dumas <[email protected]> wrote: >> Why wouldn't the config.h exist? > > It should exist in general, but if for some reason it does not, there > will be no easy way to understand that a change in behaviour or an error > happens because the config.h file included is the perl one and not the > one done by configure. > > It is not for the common cases, but an extra security, and I only raise > that issue because the config.h file from perl is in a directory > searched for by the preprocessor, if not I wouldn't propose that. Also > I raise that issue because it happened to me, when doing the standalone > module, it compiled while it shouldn't have.
I thought it shouldn't happen because of the HAVE_CONFIG_H guard that you added. If you don't think that's enough, feel free to change it.
