Sivan Toledo wrote: > A few more details on the crash with the qt-x11+gcc-2.95.3+cygwin > build that I reported a few days ago. > > I traced (with the help of my wife) the crash to the call to > std:getline in support/filetools.C, and I was able to duplicate the > crash with a very short program. This happens with gcc-2.95.3 but > not with gcc-3.3.1 on cygwin. So I think that there is some bug in > this function (std::getline) in this version of gcc. The function is > coming from a template in bastring.cc. > > I am using 2.95 since I was not able to compile Qt with 3.3. > > Another workaround that I tried is to use --with-included-string in > the configure setup, but that failed because boost insisted on > trying to > #include <limit>. > > If anybody has an idea, either on how to fix or get around the > getline bug, or how to build lyx with --witn-included-string (which > I think will use another getline), please let me know.
The gcc-2.95 version of the STL (specifically the streams part which includes std::getline) is completely non-standard. LyX 1.4.x will no longer compile using gcc-2.95's version of the STL. That's not to say gcc-2.95 has been dropped: people here are compiling lyx 1.4.x with a combination of gcc-2.95 and the STLPort version of the STL. There are a number of threads on this ml about the steps that they needed to take to get the compiler and STLPort's library working happily together. Executive summary: they succeeded ;-) If you're going to stick with gcc-2.95-3, then I recommend that you ditch the gcc version of the STL and use STLPort's instead. The effort you put in won't be wasted, because you'll be able thereafter to compile lyx 1.4.x on cygwin too. -- Angus
