Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 09-Oct-2000 John Levon wrote:
| >
| > I got this as a result of the -fhonor-std flag - it means that the simple
| > string test fails with "string undeclared", so it thinks the actual
| > implementation is buggy. Remove -fhonor-std and it will go away (at least
| > it did for me). Latest CVS I noticed doesn't set honor-std for 2.96 anyway
| > ...
|
| I don't think that that would work!
|
| But with the option --without-included-string I'm now able to compile and
| link lyx. I had to change the code in debug.h and insert ANY inside the
| enum
|
| ANY = 0xffffffff
You are allowed to post some compiler messages...
Seems to me to be a compiler bug.
And we don't want ANY defined like that...
| and comment out the code:
| #if 0
| ///
| static const type ANY = type(INFO | INIT | KEY | GUI |
| PARSER | LYXRC | KBMAP | LATEX |
| MATHED | FONT | TCLASS | LYXVC |
| LYXSERVER | ROFF | ACTION | LYXLEX |
| DEPEND | INSETS);
| #endif
|
| Lars could you comment on this please.
compiler messages please.
Lgb
