All right, let's clear all this up. The problem is xforms.
> > This is the one mentioned on the Lyx wiki and by supported I meant in > this case a precompiled binary which is a major contribution, as you'll see. > > March 26, 2003 > Claus Hentschel wrote: Current release 1.3.1 is now available for > Windows, too. Download as usual from this URL. > > "This release is based on XForms 1.0 and again compiled using the old > gcc 2.95-10 "out-of-the-box". Building Lyx using the current gcc 3.2 > from Cygwin is not possible at the moment because XForms 1.0 can't > be build using that compiler. Also building a Qt-based version of Lyx > 1.3.1 was not possible due to some strange errors while linking." > > SH: Since Jim said he was using Qt, this led me to the conclusion that > he was not using Lyx 1.3.1. Which means he is using newer versions > of LyX. Jim may be an experienced LyX, but I think he is not an expert > sys admin, due to the way he reported this problem. For instance, he > didn't mention the version(s) of LyX being used; I inferred this from > the version(s) of freebsd being used. This view leads me to suspect that > Jim would have a hard time figuring out how to build LyX from sources > on Cygwin. That is why I quoted from cygwin.com I do use Qt, but as it turns out the version of LyX I was running [1.3.6] was using xforms rather than Qt. [I mistakenly thought this installation was running Qt]. I deinstalled LyX, and reinstalled it using Qt rather than xforms and now it works fine. LyX was never running on the Cygwin machines--they were acting as Xservers, and the LyX server was serving up LyX as an X client. The Black LyX would be displayed no matter if the X server was cygwin, FreeBSD or OpenBSD. Part of the beauty of FreeBSD is the portupgrade system. LyX was originally installed a couple of years ago as ver 1.1 [?], and was portupgraded as needed. That's how I ended up with ver 1.3.6 using xforms. Also part of the 'gotchas' of the portupgrade system. -- 72, Jim N0OCT
