On Tue, 4 Oct 2005 15:43:24 -0700 "Stephen Harris" <[EMAIL PROTECTED]> wrote:
> 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 Never stated that I was running LyX on cygwin. The cygwin and other workstations are all Xservers, and the machine that is the LyX server runs it as an X client to the workstations [X servers] over a network. Inferring the version of LyX from the version of FreeBSD would be pretty tricky--I could have a fully updated FreeBSD 4.11 system running LyX 1.3.1 without too much problem [except, of course, for the blackness]. The OS is made current with -stable once a quarter [more frequently if security issues warant it], but not necessarily all the p packages and ports. I did upgrade LyX using the portupgrade mechanism which uses the options originally selected from the first install. The mistake here is that [as I understand it] Qt wasn't an option until relatively recently, and since xforms was selected by default from the initial build, the upgrade built that way as well. Deinstalling it, and building it with Qt has fixed the problem, so now all is well. Sorry for the 'confusement' as they say Down South. . . -- 72, Jim N0OCT
