Duncan Simpson <[EMAIL PROTECTED]> writes:
| LyX 1.1.5cvs prudces the followng message when compiled with the latest
| egcs/gcc 2.96 (which will be required on linux if LyX pulls out all the modern
| C++ stops).
|
| buffer.C:830:60: warning: #warning Verify that this else clause is still
| needed. (Lgb)
| buffer.C: In method `void Buffer::SimpleLinuxDocOnePar (ostream &,
| buffer.C: LyXParagraph *, int, int)':
| buffer.C:3270: Internal compiler error in `instantiate_virtual_regs_1',
| buffer.C:3270: at function.c:3844
| buffer.C:3270: Please submit a full bug report.
| buffer.C:3270: See <URL:http://www.gnu.org/software/gcc/bugs.html> for
| buffer.C:3270: instructions.
| make[3]: *** [buffer.o] Error 1
|
| gcc version is
|
| Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/2.96/specs
| gcc version 2.96 20000312 (experimental)
|
| which is up to the minute. Earlier versions have produced similar results,
| although on a more files (eveything else compiles now). Yes, I know it is a
| compiler bug and not a LyX one.
|
| LyX sources that cause all compilers new enough to cope with the C++ features
| segfaulting might limit popularity. Compiling the remainder with gcc 2.95.x
| (also the latest version) excercised an optimiser bug, resilting in code which
| just dumps core, last time I looked (no human help required). Assuming I
| actually want to test the latest version, fix some bugs and add some features
| this is a problem.
|
| Incidently according to my computer science degree the CS benefits of the
| latest C++ features (and OO in general) are minimal. Complexifying the control
| flow is actually a lot of steps in the wrong direction. My BA comes from a
| small english university called Oxford :-)
Ever looked at the gcc changelogs? They are chaning code at a rapid
pace and I have been able to compile LyX with gcc 2.96 on occasion ,
but never been able to run (segfault). Blame the compiler/libs but not
LyX.
Lgb
