[Top][All Lists]

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

Re: bison-20001221

From: Akim Demaille
Subject: Re: bison-20001221
Date: 18 Jan 2001 12:25:47 +0100
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Crater Lake)

>>>>> "Hans" == Hans Aberg <address@hidden> writes:

>> # The package should `#include' the configuration header file
>> before # any other header files, to prevent inconsistencies in
>> declarations (for # example, if it redefines `const').  Use
>> `#include <config.h>' instead # of `#include "config.h"', and pass
>> the C compiler a `-I.' option (or # `-I..'; whichever directory
>> contains `config.h').  That way, even if # the source directory is
>> configured itself (perhaps to make a # distribution), other build
>> directories can also be configured without # finding the `config.h'
>> from the source directory.

Hans> The situation described here seems to be that a directory with a
Hans> `config.h' file is used as a source directory, and one wants to
Hans> build it from another directory using a different `config.h'
Hans> file. This will then work if one is using a compiler having a
Hans> `-I' option, but not otherwise. -- I figure that this option
Hans> adds the named directory to the standard search places.

Exactly.  The problem is when there are several config.h, to make sure
you pick the right one.

But again, please don't debate on Bison's list of issue which are in
no way related to Bison.

reply via email to

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