On Apr 16, 2013, at 6:05 PM, Bruce Dubbs wrote:
I'm glad you figured this out. I was wondering about it because I'd
expect a compile error if two #defines for the same token were made
without an #undef in between.
-- Bruce
While we are on topic with Bison, it has come to my attention that
William Harrington wrote:
>
> On Apr 12, 2013, at 6:40 PM, William Harrington wrote:
>
>> echo '#define YYENABLE_NLS 1' >> lib/config.h
>>
>> After executing ./configure --prefix=/usr and viewing lib/config.h
>> #define ENABLE_NLS 1 is already there. I noticed this when upgrading
>> bison for CLFS
On Apr 12, 2013, at 6:40 PM, William Harrington wrote:
echo '#define YYENABLE_NLS 1' >> lib/config.h
After executing ./configure --prefix=/usr and viewing lib/config.h
#define ENABLE_NLS 1 is already there. I noticed this when upgrading
bison for CLFS back at version 2.6.2.
There is no need to
In the development book there exists this:
The configure system causes Bison to be built without support for
internationalization of error messages if a bison program is not
already in $PATH. The following addition will correct this:
echo '#define YYENABLE_NLS 1' >> lib/config.h
After execut
