Re: LyX and Cygwin
Thanks again for your advice. I am having a few issues with installation: In step 4 of the installation instructions (In the Select Packages view...) I did not initially see lyx and related packages. After clicking View a few times until Not Installed was displayed, the relevant packages were displayed (lyx, lyxdict, etc, although not LyXwin as stated in step 4). When installing, I then got popup messages from Cygwin setup Can't open (null) for reading: No such file while setup was installing cygspawn-1.0.0-2-src, dtltools-0.6.2-src, dvipost-1.1-4-src, latex2rtf-1.9.17-2.src, lyxsupport-2.0-src. Finally, lyx still finds my windows installation rather than the new cygwin version: $ lyx -version LyX 2.0.8 (2014-04-14) Built on Apr 15 2014, 23:03:32 CMake Build I'm assuming I need to edit the cygwin PATH variable, since this still includes /cygdrive/c/Program Files (x86)/LyX 2.0/bin however, I can't find the right directory in cygwin, i.e. /usr/local/share/lyx/ does not exist, nor can I find lyx.exe, lyxwin.exe, or any lyx directory in my cygwin installation. I'm not sure that I've looked everywhere, but I have looked everywhere I can think of, including C:\cygwin64\bin C:\cygwin64\etc C:\cygwin64\lib C:\cygwin64\usr C:\cygwin64\usr\local C:\cygwin64\usr\share which leads me to suspect my installation was not successful after all. Any suggestions?
Re: LyX and Cygwin
On Mon, May 05, 2014 at 11:13:18AM -0400, Bert Lloyd wrote: Thanks again for your advice. I am having a few issues with installation: In step 4 of the installation instructions (In the Select Packages view...) I did not initially see lyx and related packages. After clicking View a few times until Not Installed was displayed, the relevant packages were displayed (lyx, lyxdict, etc, although not LyXwin as stated in step 4). When installing, I then got popup messages from Cygwin setup Can't open (null) for reading: No such file while setup was installing cygspawn-1.0.0-2-src, dtltools-0.6.2-src, dvipost-1.1-4-src, latex2rtf-1.9.17-2.src, lyxsupport-2.0-src. Finally, lyx still finds my windows installation rather than the new cygwin version: $ lyx -version LyX 2.0.8 (2014-04-14) Built on Apr 15 2014, 23:03:32 CMake Build I'm assuming I need to edit the cygwin PATH variable, since this still includes /cygdrive/c/Program Files (x86)/LyX 2.0/bin however, I can't find the right directory in cygwin, i.e. /usr/local/share/lyx/ does not exist, nor can I find lyx.exe, lyxwin.exe, or any lyx directory in my cygwin installation. I'm not sure that I've looked everywhere, but I have looked everywhere I can think of, including C:\cygwin64\bin C:\cygwin64\etc C:\cygwin64\lib C:\cygwin64\usr C:\cygwin64\usr\local C:\cygwin64\usr\share which leads me to suspect my installation was not successful after all. Any suggestions? From what you write above, I suspect that you installed the 64 bit version of Cygwin, while that package was built for the 32 bit version. If you don't have a specific need for the 64 bit version, you can try installing the 32 bit version. I am sorry but I don't have cygwin64 and can't build a 64 bit version of the package ATM, because I still use an old 32 bit laptop for working in Windows. -- Enrico
Re: LyX and Cygwin
Thanks, installing 32-bit Cygwin solved the problem. On Mon, May 5, 2014 at 1:38 PM, Enrico Forestieri for...@lyx.org wrote: On Mon, May 05, 2014 at 11:13:18AM -0400, Bert Lloyd wrote: Thanks again for your advice. I am having a few issues with installation: In step 4 of the installation instructions (In the Select Packages view...) I did not initially see lyx and related packages. After clicking View a few times until Not Installed was displayed, the relevant packages were displayed (lyx, lyxdict, etc, although not LyXwin as stated in step 4). When installing, I then got popup messages from Cygwin setup Can't open (null) for reading: No such file while setup was installing cygspawn-1.0.0-2-src, dtltools-0.6.2-src, dvipost-1.1-4-src, latex2rtf-1.9.17-2.src, lyxsupport-2.0-src. Finally, lyx still finds my windows installation rather than the new cygwin version: $ lyx -version LyX 2.0.8 (2014-04-14) Built on Apr 15 2014, 23:03:32 CMake Build I'm assuming I need to edit the cygwin PATH variable, since this still includes /cygdrive/c/Program Files (x86)/LyX 2.0/bin however, I can't find the right directory in cygwin, i.e. /usr/local/share/lyx/ does not exist, nor can I find lyx.exe, lyxwin.exe, or any lyx directory in my cygwin installation. I'm not sure that I've looked everywhere, but I have looked everywhere I can think of, including C:\cygwin64\bin C:\cygwin64\etc C:\cygwin64\lib C:\cygwin64\usr C:\cygwin64\usr\local C:\cygwin64\usr\share which leads me to suspect my installation was not successful after all. Any suggestions? From what you write above, I suspect that you installed the 64 bit version of Cygwin, while that package was built for the 32 bit version. If you don't have a specific need for the 64 bit version, you can try installing the 32 bit version. I am sorry but I don't have cygwin64 and can't build a 64 bit version of the package ATM, because I still use an old 32 bit laptop for working in Windows. -- Enrico
Re: LyX and Cygwin
Thanks again for your advice. I am having a few issues with installation: In step 4 of the installation instructions (In the Select Packages view...) I did not initially see lyx and related packages. After clicking View a few times until Not Installed was displayed, the relevant packages were displayed (lyx, lyxdict, etc, although not LyXwin as stated in step 4). When installing, I then got popup messages from Cygwin setup Can't open (null) for reading: No such file while setup was installing cygspawn-1.0.0-2-src, dtltools-0.6.2-src, dvipost-1.1-4-src, latex2rtf-1.9.17-2.src, lyxsupport-2.0-src. Finally, lyx still finds my windows installation rather than the new cygwin version: $ lyx -version LyX 2.0.8 (2014-04-14) Built on Apr 15 2014, 23:03:32 CMake Build I'm assuming I need to edit the cygwin PATH variable, since this still includes /cygdrive/c/Program Files (x86)/LyX 2.0/bin however, I can't find the right directory in cygwin, i.e. /usr/local/share/lyx/ does not exist, nor can I find lyx.exe, lyxwin.exe, or any lyx directory in my cygwin installation. I'm not sure that I've looked everywhere, but I have looked everywhere I can think of, including C:\cygwin64\bin C:\cygwin64\etc C:\cygwin64\lib C:\cygwin64\usr C:\cygwin64\usr\local C:\cygwin64\usr\share which leads me to suspect my installation was not successful after all. Any suggestions?
Re: LyX and Cygwin
On Mon, May 05, 2014 at 11:13:18AM -0400, Bert Lloyd wrote: Thanks again for your advice. I am having a few issues with installation: In step 4 of the installation instructions (In the Select Packages view...) I did not initially see lyx and related packages. After clicking View a few times until Not Installed was displayed, the relevant packages were displayed (lyx, lyxdict, etc, although not LyXwin as stated in step 4). When installing, I then got popup messages from Cygwin setup Can't open (null) for reading: No such file while setup was installing cygspawn-1.0.0-2-src, dtltools-0.6.2-src, dvipost-1.1-4-src, latex2rtf-1.9.17-2.src, lyxsupport-2.0-src. Finally, lyx still finds my windows installation rather than the new cygwin version: $ lyx -version LyX 2.0.8 (2014-04-14) Built on Apr 15 2014, 23:03:32 CMake Build I'm assuming I need to edit the cygwin PATH variable, since this still includes /cygdrive/c/Program Files (x86)/LyX 2.0/bin however, I can't find the right directory in cygwin, i.e. /usr/local/share/lyx/ does not exist, nor can I find lyx.exe, lyxwin.exe, or any lyx directory in my cygwin installation. I'm not sure that I've looked everywhere, but I have looked everywhere I can think of, including C:\cygwin64\bin C:\cygwin64\etc C:\cygwin64\lib C:\cygwin64\usr C:\cygwin64\usr\local C:\cygwin64\usr\share which leads me to suspect my installation was not successful after all. Any suggestions? From what you write above, I suspect that you installed the 64 bit version of Cygwin, while that package was built for the 32 bit version. If you don't have a specific need for the 64 bit version, you can try installing the 32 bit version. I am sorry but I don't have cygwin64 and can't build a 64 bit version of the package ATM, because I still use an old 32 bit laptop for working in Windows. -- Enrico
Re: LyX and Cygwin
Thanks, installing 32-bit Cygwin solved the problem. On Mon, May 5, 2014 at 1:38 PM, Enrico Forestieri for...@lyx.org wrote: On Mon, May 05, 2014 at 11:13:18AM -0400, Bert Lloyd wrote: Thanks again for your advice. I am having a few issues with installation: In step 4 of the installation instructions (In the Select Packages view...) I did not initially see lyx and related packages. After clicking View a few times until Not Installed was displayed, the relevant packages were displayed (lyx, lyxdict, etc, although not LyXwin as stated in step 4). When installing, I then got popup messages from Cygwin setup Can't open (null) for reading: No such file while setup was installing cygspawn-1.0.0-2-src, dtltools-0.6.2-src, dvipost-1.1-4-src, latex2rtf-1.9.17-2.src, lyxsupport-2.0-src. Finally, lyx still finds my windows installation rather than the new cygwin version: $ lyx -version LyX 2.0.8 (2014-04-14) Built on Apr 15 2014, 23:03:32 CMake Build I'm assuming I need to edit the cygwin PATH variable, since this still includes /cygdrive/c/Program Files (x86)/LyX 2.0/bin however, I can't find the right directory in cygwin, i.e. /usr/local/share/lyx/ does not exist, nor can I find lyx.exe, lyxwin.exe, or any lyx directory in my cygwin installation. I'm not sure that I've looked everywhere, but I have looked everywhere I can think of, including C:\cygwin64\bin C:\cygwin64\etc C:\cygwin64\lib C:\cygwin64\usr C:\cygwin64\usr\local C:\cygwin64\usr\share which leads me to suspect my installation was not successful after all. Any suggestions? From what you write above, I suspect that you installed the 64 bit version of Cygwin, while that package was built for the 32 bit version. If you don't have a specific need for the 64 bit version, you can try installing the 32 bit version. I am sorry but I don't have cygwin64 and can't build a 64 bit version of the package ATM, because I still use an old 32 bit laptop for working in Windows. -- Enrico
Re: LyX and Cygwin
Thanks again for your advice.
I am having a few issues with installation:
In step 4 of the installation instructions ("In the "Select Packages"
view...") I did not initially see lyx and related packages. After
clicking "View" a few times until "Not Installed" was displayed, the
relevant packages were displayed (lyx, lyxdict, etc, although not
LyXwin as stated in step 4).
When installing, I then got popup messages from Cygwin setup "Can't
open (null) for reading: No such file" while setup was installing
cygspawn-1.0.0-2-src, dtltools-0.6.2-src, dvipost-1.1-4-src,
latex2rtf-1.9.17-2.src, lyxsupport-2.0-src.
Finally, lyx still finds my windows installation rather than the new
cygwin version:
$ lyx -version
LyX 2.0.8 (2014-04-14)
Built on Apr 15 2014, 23:03:32
CMake Build
I'm assuming I need to edit the cygwin PATH variable, since this still includes
/cygdrive/c/Program Files (x86)/LyX 2.0/bin
however, I can't find the right directory in cygwin, i.e.
/usr/local/share/lyx/ does not exist, nor can I find lyx.exe,
lyxwin.exe, or any lyx directory in my cygwin installation. I'm not
sure that I've looked everywhere, but I have looked everywhere I can
think of, including
C:\cygwin64\bin
C:\cygwin64\etc
C:\cygwin64\lib
C:\cygwin64\usr
C:\cygwin64\usr\local
C:\cygwin64\usr\share
which leads me to suspect my installation was not successful after all.
Any suggestions?
Re: LyX and Cygwin
On Mon, May 05, 2014 at 11:13:18AM -0400, Bert Lloyd wrote:
> Thanks again for your advice.
>
> I am having a few issues with installation:
>
> In step 4 of the installation instructions ("In the "Select Packages"
> view...") I did not initially see lyx and related packages. After
> clicking "View" a few times until "Not Installed" was displayed, the
> relevant packages were displayed (lyx, lyxdict, etc, although not
> LyXwin as stated in step 4).
>
> When installing, I then got popup messages from Cygwin setup "Can't
> open (null) for reading: No such file" while setup was installing
> cygspawn-1.0.0-2-src, dtltools-0.6.2-src, dvipost-1.1-4-src,
> latex2rtf-1.9.17-2.src, lyxsupport-2.0-src.
>
> Finally, lyx still finds my windows installation rather than the new
> cygwin version:
> $ lyx -version
> LyX 2.0.8 (2014-04-14)
> Built on Apr 15 2014, 23:03:32
> CMake Build
>
>
> I'm assuming I need to edit the cygwin PATH variable, since this still
> includes
> /cygdrive/c/Program Files (x86)/LyX 2.0/bin
> however, I can't find the right directory in cygwin, i.e.
> /usr/local/share/lyx/ does not exist, nor can I find lyx.exe,
> lyxwin.exe, or any lyx directory in my cygwin installation. I'm not
> sure that I've looked everywhere, but I have looked everywhere I can
> think of, including
> C:\cygwin64\bin
> C:\cygwin64\etc
> C:\cygwin64\lib
> C:\cygwin64\usr
> C:\cygwin64\usr\local
> C:\cygwin64\usr\share
>
> which leads me to suspect my installation was not successful after all.
>
> Any suggestions?
>From what you write above, I suspect that you installed the 64 bit version
of Cygwin, while that package was built for the 32 bit version.
If you don't have a specific need for the 64 bit version, you can try
installing the 32 bit version. I am sorry but I don't have cygwin64
and can't build a 64 bit version of the package ATM, because I still
use an old 32 bit laptop for working in Windows.
--
Enrico
Re: LyX and Cygwin
Thanks, installing 32-bit Cygwin solved the problem.
On Mon, May 5, 2014 at 1:38 PM, Enrico Forestieri <for...@lyx.org> wrote:
> On Mon, May 05, 2014 at 11:13:18AM -0400, Bert Lloyd wrote:
>
>> Thanks again for your advice.
>>
>> I am having a few issues with installation:
>>
>> In step 4 of the installation instructions ("In the "Select Packages"
>> view...") I did not initially see lyx and related packages. After
>> clicking "View" a few times until "Not Installed" was displayed, the
>> relevant packages were displayed (lyx, lyxdict, etc, although not
>> LyXwin as stated in step 4).
>>
>> When installing, I then got popup messages from Cygwin setup "Can't
>> open (null) for reading: No such file" while setup was installing
>> cygspawn-1.0.0-2-src, dtltools-0.6.2-src, dvipost-1.1-4-src,
>> latex2rtf-1.9.17-2.src, lyxsupport-2.0-src.
>>
>> Finally, lyx still finds my windows installation rather than the new
>> cygwin version:
>> $ lyx -version
>> LyX 2.0.8 (2014-04-14)
>> Built on Apr 15 2014, 23:03:32
>> CMake Build
>>
>>
>> I'm assuming I need to edit the cygwin PATH variable, since this still
>> includes
>> /cygdrive/c/Program Files (x86)/LyX 2.0/bin
>> however, I can't find the right directory in cygwin, i.e.
>> /usr/local/share/lyx/ does not exist, nor can I find lyx.exe,
>> lyxwin.exe, or any lyx directory in my cygwin installation. I'm not
>> sure that I've looked everywhere, but I have looked everywhere I can
>> think of, including
>> C:\cygwin64\bin
>> C:\cygwin64\etc
>> C:\cygwin64\lib
>> C:\cygwin64\usr
>> C:\cygwin64\usr\local
>> C:\cygwin64\usr\share
>>
>> which leads me to suspect my installation was not successful after all.
>>
>> Any suggestions?
>
> From what you write above, I suspect that you installed the 64 bit version
> of Cygwin, while that package was built for the 32 bit version.
> If you don't have a specific need for the 64 bit version, you can try
> installing the 32 bit version. I am sorry but I don't have cygwin64
> and can't build a 64 bit version of the package ATM, because I still
> use an old 32 bit laptop for working in Windows.
>
> --
> Enrico
Re: LyX and Cygwin
Dear Enrico, Thank you for your thoughtful reply. I have two clarifying questions, interspersed below. Best, BL On Fri, May 2, 2014 at 10:40 PM, Enrico Forestieri for...@lyx.org wrote: Bert Lloyd writes: Dear LyX-users, I am writing some scripts to create PDFs from a number of LyX files. I use Windows, but to maximize cross-platform portability, I'm writing the scripts for Cygwin so that they can run on unix and MacOS. I would like to know whether one of the following three options is preferable: 1. Add my current Windows installation of LyX and MikTeX to my Cygwin PATH variable, so cygwin can find lyx.exe, etc. This works provided that you take into account that a native version of LyX cannot use neither scripts nor commands that are symlinks. If you need one of such commands you have to write a wrapper batch file. Often, they can be one liners of the kind @bash -c 'script_or_symlink_name %*' Do you mean a native version of LyX (a) cannot use scripts and (b) cannot use commands that are symlinks or a native version of LyX (a) cannot use scripts that are (contain?) symlinks (but could use scripts that do not contain symlinks) and (b) cannot use commands that are symlinks 2. In Cygwin, install the most recent version of LyX (and, presumably, texlive or some other latex engine) and run the cygwin scripts using these. While there can be some issues using a Cygwin TeX engine with a native LyX version (but it can be done), a Cygwin version of LyX can use without problems a native TeX engine. So, if you install LyX/Cygwin and already have, say MikTeX, you don't need installing texlive in Cygwin. 3. Download the tar.gz Cygwin binary directly from http://www.lyx.org/Download and [install? compile?] it. This is currently a bit beyond my ability, although I could learn. That tar.gz contains a Cygwin package to be installed through the setup.exe installation tool. Simply untar it (using the Cygwin tar version, not a native one) and follow the instructions in the README file. This version does not use an X server and is visually identical to the native version. Any other general tips for Cygwin and LyX are of course appreciated. If you already use Cygwin, then install the Cygwin version of LyX. If you only sporadically need Cygwin, then install the native version of LyX and use wrapper batch files to call the commands you need. If you need interoperability with unix and MacOS, then definitely install the Cygwin version of LyX. I'm just doing very simple things in these script: lyx -e to export to tex, ultra-simple sed commands to change a couple of lines in the tex-file (e.g. notes=show to notes=hide in beamer), then pdflatex to compile pdfs. My belief was that these were simple enough to be consistent between native LyX and Cygwin LyX (indeed, only the first is a lyx command). Is this belief reasonable?
Re: LyX and Cygwin
On Sat, May 03, 2014 at 10:42:12AM -0400, Bert Lloyd wrote: On Fri, May 2, 2014 at 10:40 PM, Enrico Forestieri for...@lyx.org wrote: Bert Lloyd writes: 1. Add my current Windows installation of LyX and MikTeX to my Cygwin PATH variable, so cygwin can find lyx.exe, etc. This works provided that you take into account that a native version of LyX cannot use neither scripts nor commands that are symlinks. If you need one of such commands you have to write a wrapper batch file. Often, they can be one liners of the kind @bash -c 'script_or_symlink_name %*' Do you mean a native version of LyX (a) cannot use scripts and (b) cannot use commands that are symlinks Yes, scripts and symlinks cannot be directly executed by a native program. I'm just doing very simple things in these script: lyx -e to export to tex, ultra-simple sed commands to change a couple of lines in the tex-file (e.g. notes=show to notes=hide in beamer), then pdflatex to compile pdfs. My belief was that these were simple enough to be consistent between native LyX and Cygwin LyX (indeed, only the first is a lyx command). Is this belief reasonable? Yes, for these simple things both versions are suitable. However, I think that the official native LyX is compiled as a GUI application. If so, you will not get any output on the terminal and thus will not see any error message. Also, a GUI application launched from a terminal (or script) generally returns immediately and this may be a problem. Your calling script should be prepared for this. For example, the command lyx -e pdf document.lyx may return before document.pdf is produced. Thus, you have to check that document.pdf actually is created before continuing with other commands. But you are not notified if an error occurs and your script may wait forever for the result... Well, native GUI commands are not comfortable for scripting. -- Enrico
Re: LyX and Cygwin
Dear Enrico, Thank you for your thoughtful reply. I have two clarifying questions, interspersed below. Best, BL On Fri, May 2, 2014 at 10:40 PM, Enrico Forestieri for...@lyx.org wrote: Bert Lloyd writes: Dear LyX-users, I am writing some scripts to create PDFs from a number of LyX files. I use Windows, but to maximize cross-platform portability, I'm writing the scripts for Cygwin so that they can run on unix and MacOS. I would like to know whether one of the following three options is preferable: 1. Add my current Windows installation of LyX and MikTeX to my Cygwin PATH variable, so cygwin can find lyx.exe, etc. This works provided that you take into account that a native version of LyX cannot use neither scripts nor commands that are symlinks. If you need one of such commands you have to write a wrapper batch file. Often, they can be one liners of the kind @bash -c 'script_or_symlink_name %*' Do you mean a native version of LyX (a) cannot use scripts and (b) cannot use commands that are symlinks or a native version of LyX (a) cannot use scripts that are (contain?) symlinks (but could use scripts that do not contain symlinks) and (b) cannot use commands that are symlinks 2. In Cygwin, install the most recent version of LyX (and, presumably, texlive or some other latex engine) and run the cygwin scripts using these. While there can be some issues using a Cygwin TeX engine with a native LyX version (but it can be done), a Cygwin version of LyX can use without problems a native TeX engine. So, if you install LyX/Cygwin and already have, say MikTeX, you don't need installing texlive in Cygwin. 3. Download the tar.gz Cygwin binary directly from http://www.lyx.org/Download and [install? compile?] it. This is currently a bit beyond my ability, although I could learn. That tar.gz contains a Cygwin package to be installed through the setup.exe installation tool. Simply untar it (using the Cygwin tar version, not a native one) and follow the instructions in the README file. This version does not use an X server and is visually identical to the native version. Any other general tips for Cygwin and LyX are of course appreciated. If you already use Cygwin, then install the Cygwin version of LyX. If you only sporadically need Cygwin, then install the native version of LyX and use wrapper batch files to call the commands you need. If you need interoperability with unix and MacOS, then definitely install the Cygwin version of LyX. I'm just doing very simple things in these script: lyx -e to export to tex, ultra-simple sed commands to change a couple of lines in the tex-file (e.g. notes=show to notes=hide in beamer), then pdflatex to compile pdfs. My belief was that these were simple enough to be consistent between native LyX and Cygwin LyX (indeed, only the first is a lyx command). Is this belief reasonable?
Re: LyX and Cygwin
On Sat, May 03, 2014 at 10:42:12AM -0400, Bert Lloyd wrote: On Fri, May 2, 2014 at 10:40 PM, Enrico Forestieri for...@lyx.org wrote: Bert Lloyd writes: 1. Add my current Windows installation of LyX and MikTeX to my Cygwin PATH variable, so cygwin can find lyx.exe, etc. This works provided that you take into account that a native version of LyX cannot use neither scripts nor commands that are symlinks. If you need one of such commands you have to write a wrapper batch file. Often, they can be one liners of the kind @bash -c 'script_or_symlink_name %*' Do you mean a native version of LyX (a) cannot use scripts and (b) cannot use commands that are symlinks Yes, scripts and symlinks cannot be directly executed by a native program. I'm just doing very simple things in these script: lyx -e to export to tex, ultra-simple sed commands to change a couple of lines in the tex-file (e.g. notes=show to notes=hide in beamer), then pdflatex to compile pdfs. My belief was that these were simple enough to be consistent between native LyX and Cygwin LyX (indeed, only the first is a lyx command). Is this belief reasonable? Yes, for these simple things both versions are suitable. However, I think that the official native LyX is compiled as a GUI application. If so, you will not get any output on the terminal and thus will not see any error message. Also, a GUI application launched from a terminal (or script) generally returns immediately and this may be a problem. Your calling script should be prepared for this. For example, the command lyx -e pdf document.lyx may return before document.pdf is produced. Thus, you have to check that document.pdf actually is created before continuing with other commands. But you are not notified if an error occurs and your script may wait forever for the result... Well, native GUI commands are not comfortable for scripting. -- Enrico
Re: LyX and Cygwin
Dear Enrico, Thank you for your thoughtful reply. I have two clarifying questions, interspersed below. Best, BL On Fri, May 2, 2014 at 10:40 PM, Enrico Forestieri <for...@lyx.org> wrote: > Bert Lloyd writes: >> >> Dear LyX-users, >> >> I am writing some scripts to create PDFs from a number of LyX files. I >> use Windows, but to maximize cross-platform portability, I'm writing >> the scripts for Cygwin so that they can run on unix and MacOS. I would >> like to know whether one of the following three options is preferable: >> >> 1. Add my current Windows installation of LyX and MikTeX to my Cygwin >> PATH variable, so cygwin can find lyx.exe, etc. > > This works provided that you take into account that a native version > of LyX cannot use neither scripts nor commands that are symlinks. > If you need one of such commands you have to write a wrapper batch > file. Often, they can be one liners of the kind > > @bash -c 'script_or_symlink_name %*' > Do you mean "a native version of LyX (a) cannot use scripts and (b) cannot use commands that are symlinks" or "a native version of LyX (a) cannot use scripts that are (contain?) symlinks (but could use scripts that do not contain symlinks) and (b) cannot use commands that are symlinks" >> 2. In Cygwin, install the most recent version of LyX (and, presumably, >> texlive or some other latex engine) and run the cygwin scripts using >> these. > > While there can be some issues using a Cygwin TeX engine with a native > LyX version (but it can be done), a Cygwin version of LyX can use > without problems a native TeX engine. So, if you install LyX/Cygwin > and already have, say MikTeX, you don't need installing texlive in Cygwin. > >> 3. Download the tar.gz Cygwin binary directly from >> http://www.lyx.org/Download and [install? compile?] it. This is >> currently a bit beyond my ability, although I could learn. > > That tar.gz contains a Cygwin package to be installed through the > setup.exe installation tool. Simply untar it (using the Cygwin tar > version, not a native one) and follow the instructions in the README > file. This version does not use an X server and is visually identical > to the native version. > >> Any other general tips for Cygwin and LyX are of course appreciated. > > If you already use Cygwin, then install the Cygwin version of LyX. > If you only sporadically need Cygwin, then install the native version > of LyX and use wrapper batch files to call the commands you need. > If you need interoperability with unix and MacOS, then definitely > install the Cygwin version of LyX. > I'm just doing very simple things in these script: lyx -e to export to tex, ultra-simple sed commands to change a couple of lines in the tex-file (e.g. notes=show to notes=hide in beamer), then pdflatex to compile pdfs. My belief was that these were simple enough to be consistent between native LyX and Cygwin LyX (indeed, only the first is a lyx command). Is this belief reasonable?
Re: LyX and Cygwin
On Sat, May 03, 2014 at 10:42:12AM -0400, Bert Lloyd wrote: > > On Fri, May 2, 2014 at 10:40 PM, Enrico Forestieri <for...@lyx.org> wrote: > > Bert Lloyd writes: > >> > >> 1. Add my current Windows installation of LyX and MikTeX to my Cygwin > >> PATH variable, so cygwin can find lyx.exe, etc. > > > > This works provided that you take into account that a native version > > of LyX cannot use neither scripts nor commands that are symlinks. > > If you need one of such commands you have to write a wrapper batch > > file. Often, they can be one liners of the kind > > > > @bash -c 'script_or_symlink_name %*' > > > > Do you mean > > "a native version of LyX (a) cannot use scripts and (b) cannot use > commands that are symlinks" Yes, scripts and symlinks cannot be directly executed by a native program. > I'm just doing very simple things in these script: lyx -e to export to > tex, ultra-simple sed commands to change a couple of lines in the > tex-file (e.g. notes=show to notes=hide in beamer), then pdflatex to > compile pdfs. > > My belief was that these were simple enough to be consistent between > native LyX and Cygwin LyX (indeed, only the first is a lyx command). > Is this belief reasonable? Yes, for these simple things both versions are suitable. However, I think that the official native LyX is compiled as a GUI application. If so, you will not get any output on the terminal and thus will not see any error message. Also, a GUI application launched from a terminal (or script) generally returns immediately and this may be a problem. Your calling script should be prepared for this. For example, the command "lyx -e pdf document.lyx" may return before document.pdf is produced. Thus, you have to check that document.pdf actually is created before continuing with other commands. But you are not notified if an error occurs and your script may wait forever for the result... Well, native GUI commands are not comfortable for scripting. -- Enrico
LyX and Cygwin
Dear LyX-users, I am writing some scripts to create PDFs from a number of LyX files. I use Windows, but to maximize cross-platform portability, I'm writing the scripts for Cygwin so that they can run on unix and MacOS. I would like to know whether one of the following three options is preferable: 1. Add my current Windows installation of LyX and MikTeX to my Cygwin PATH variable, so cygwin can find lyx.exe, etc. 2. In Cygwin, install the most recent version of LyX (and, presumably, texlive or some other latex engine) and run the cygwin scripts using these. 3. Download the tar.gz Cygwin binary directly from http://www.lyx.org/Download and [install? compile?] it. This is currently a bit beyond my ability, although I could learn. Any other general tips for Cygwin and LyX are of course appreciated. Thanks, BL PS - W7-64, LyX 2.0.8, MikTeX 2.9.
Re: LyX and Cygwin
Bert Lloyd writes: Dear LyX-users, I am writing some scripts to create PDFs from a number of LyX files. I use Windows, but to maximize cross-platform portability, I'm writing the scripts for Cygwin so that they can run on unix and MacOS. I would like to know whether one of the following three options is preferable: 1. Add my current Windows installation of LyX and MikTeX to my Cygwin PATH variable, so cygwin can find lyx.exe, etc. This works provided that you take into account that a native version of LyX cannot use neither scripts nor commands that are symlinks. If you need one of such commands you have to write a wrapper batch file. Often, they can be one liners of the kind @bash -c 'script_or_symlink_name %*' 2. In Cygwin, install the most recent version of LyX (and, presumably, texlive or some other latex engine) and run the cygwin scripts using these. While there can be some issues using a Cygwin TeX engine with a native LyX version (but it can be done), a Cygwin version of LyX can use without problems a native TeX engine. So, if you install LyX/Cygwin and already have, say MikTeX, you don't need installing texlive in Cygwin. 3. Download the tar.gz Cygwin binary directly from http://www.lyx.org/Download and [install? compile?] it. This is currently a bit beyond my ability, although I could learn. That tar.gz contains a Cygwin package to be installed through the setup.exe installation tool. Simply untar it (using the Cygwin tar version, not a native one) and follow the instructions in the README file. This version does not use an X server and is visually identical to the native version. Any other general tips for Cygwin and LyX are of course appreciated. If you already use Cygwin, then install the Cygwin version of LyX. If you only sporadically need Cygwin, then install the native version of LyX and use wrapper batch files to call the commands you need. If you need interoperability with unix and MacOS, then definitely install the Cygwin version of LyX. -- Enrico
LyX and Cygwin
Dear LyX-users, I am writing some scripts to create PDFs from a number of LyX files. I use Windows, but to maximize cross-platform portability, I'm writing the scripts for Cygwin so that they can run on unix and MacOS. I would like to know whether one of the following three options is preferable: 1. Add my current Windows installation of LyX and MikTeX to my Cygwin PATH variable, so cygwin can find lyx.exe, etc. 2. In Cygwin, install the most recent version of LyX (and, presumably, texlive or some other latex engine) and run the cygwin scripts using these. 3. Download the tar.gz Cygwin binary directly from http://www.lyx.org/Download and [install? compile?] it. This is currently a bit beyond my ability, although I could learn. Any other general tips for Cygwin and LyX are of course appreciated. Thanks, BL PS - W7-64, LyX 2.0.8, MikTeX 2.9.
Re: LyX and Cygwin
Bert Lloyd writes: Dear LyX-users, I am writing some scripts to create PDFs from a number of LyX files. I use Windows, but to maximize cross-platform portability, I'm writing the scripts for Cygwin so that they can run on unix and MacOS. I would like to know whether one of the following three options is preferable: 1. Add my current Windows installation of LyX and MikTeX to my Cygwin PATH variable, so cygwin can find lyx.exe, etc. This works provided that you take into account that a native version of LyX cannot use neither scripts nor commands that are symlinks. If you need one of such commands you have to write a wrapper batch file. Often, they can be one liners of the kind @bash -c 'script_or_symlink_name %*' 2. In Cygwin, install the most recent version of LyX (and, presumably, texlive or some other latex engine) and run the cygwin scripts using these. While there can be some issues using a Cygwin TeX engine with a native LyX version (but it can be done), a Cygwin version of LyX can use without problems a native TeX engine. So, if you install LyX/Cygwin and already have, say MikTeX, you don't need installing texlive in Cygwin. 3. Download the tar.gz Cygwin binary directly from http://www.lyx.org/Download and [install? compile?] it. This is currently a bit beyond my ability, although I could learn. That tar.gz contains a Cygwin package to be installed through the setup.exe installation tool. Simply untar it (using the Cygwin tar version, not a native one) and follow the instructions in the README file. This version does not use an X server and is visually identical to the native version. Any other general tips for Cygwin and LyX are of course appreciated. If you already use Cygwin, then install the Cygwin version of LyX. If you only sporadically need Cygwin, then install the native version of LyX and use wrapper batch files to call the commands you need. If you need interoperability with unix and MacOS, then definitely install the Cygwin version of LyX. -- Enrico
LyX and Cygwin
Dear LyX-users, I am writing some scripts to create PDFs from a number of LyX files. I use Windows, but to maximize cross-platform portability, I'm writing the scripts for Cygwin so that they can run on unix and MacOS. I would like to know whether one of the following three options is preferable: 1. Add my current Windows installation of LyX and MikTeX to my Cygwin PATH variable, so cygwin can find lyx.exe, etc. 2. In Cygwin, install the most recent version of LyX (and, presumably, texlive or some other latex engine) and run the cygwin scripts using these. 3. Download the tar.gz Cygwin binary directly from http://www.lyx.org/Download and [install? compile?] it. This is currently a bit beyond my ability, although I could learn. Any other general tips for Cygwin and LyX are of course appreciated. Thanks, BL PS - W7-64, LyX 2.0.8, MikTeX 2.9.
Re: LyX and Cygwin
Bert Lloyd writes: > > Dear LyX-users, > > I am writing some scripts to create PDFs from a number of LyX files. I > use Windows, but to maximize cross-platform portability, I'm writing > the scripts for Cygwin so that they can run on unix and MacOS. I would > like to know whether one of the following three options is preferable: > > 1. Add my current Windows installation of LyX and MikTeX to my Cygwin > PATH variable, so cygwin can find lyx.exe, etc. This works provided that you take into account that a native version of LyX cannot use neither scripts nor commands that are symlinks. If you need one of such commands you have to write a wrapper batch file. Often, they can be one liners of the kind @bash -c 'script_or_symlink_name %*' > 2. In Cygwin, install the most recent version of LyX (and, presumably, > texlive or some other latex engine) and run the cygwin scripts using > these. While there can be some issues using a Cygwin TeX engine with a native LyX version (but it can be done), a Cygwin version of LyX can use without problems a native TeX engine. So, if you install LyX/Cygwin and already have, say MikTeX, you don't need installing texlive in Cygwin. > 3. Download the tar.gz Cygwin binary directly from > http://www.lyx.org/Download and [install? compile?] it. This is > currently a bit beyond my ability, although I could learn. That tar.gz contains a Cygwin package to be installed through the setup.exe installation tool. Simply untar it (using the Cygwin tar version, not a native one) and follow the instructions in the README file. This version does not use an X server and is visually identical to the native version. > Any other general tips for Cygwin and LyX are of course appreciated. If you already use Cygwin, then install the Cygwin version of LyX. If you only sporadically need Cygwin, then install the native version of LyX and use wrapper batch files to call the commands you need. If you need interoperability with unix and MacOS, then definitely install the Cygwin version of LyX. -- Enrico
Lyx-1.4.3 cygwin port is officially released.
Dear lyxers, Lyx 1.4.3 has just become one of the official cygwin packages. Here is the announcement from cygwin-announce: http://www.cygwin.com/ml/cygwin-announce/2006-10/msg2.html . I just tried to install lyx through cygwin. Lyx starts fine but complains about missing texclass book. I guess I missed some tetex packages that should be listed as lyx' dependent packages. I also notice that math fonts are not working (\alpha etc) . Please test and report to me more such problems so that I can fix them in the next release of cygwin/lyx. Cheers, Bo
Lyx-1.4.3 cygwin port is officially released.
Dear lyxers, Lyx 1.4.3 has just become one of the official cygwin packages. Here is the announcement from cygwin-announce: http://www.cygwin.com/ml/cygwin-announce/2006-10/msg2.html . I just tried to install lyx through cygwin. Lyx starts fine but complains about missing texclass book. I guess I missed some tetex packages that should be listed as lyx' dependent packages. I also notice that math fonts are not working (\alpha etc) . Please test and report to me more such problems so that I can fix them in the next release of cygwin/lyx. Cheers, Bo
Lyx-1.4.3 cygwin port is officially released.
Dear lyxers, Lyx 1.4.3 has just become one of the official cygwin packages. Here is the announcement from cygwin-announce: http://www.cygwin.com/ml/cygwin-announce/2006-10/msg2.html . I just tried to install lyx through cygwin. Lyx starts fine but complains about missing texclass book. I guess I missed some tetex packages that should be listed as lyx' dependent packages. I also notice that math fonts are not working (\alpha etc) . Please test and report to me more such problems so that I can fix them in the next release of cygwin/lyx. Cheers, Bo
Re: LyX on Cygwin
Enrico Forestieri [EMAIL PROTECTED] writes: On Sat, 25 Feb 2006 14:42:04 -0800, Stephen Harris wrote: The other difference is that I have a populated TeX Information and I can send you a screenshot of it present in CygLyxWin140_5. I'm wondering if there are differences due to TeTeX vs. Miktex? No, I don't think that's the problem, it must be something else. I have an empty TeX information with both teTeX and MikTeX, and with both 1.3.7 and 1.4.0 but LyX works and so I don't care... it must be something with my environment. I found what the problem is. In the file scripts/TeXFiles.sh it is assumed that the path separator is ';' when it detects a Windows environment. Now, in cygwin the path separator is ':', instead, and that causes the empty TeX Information dialog. This is only a problem with the cygwin tetex as MikTeX always returns Windows style path lists separated by ';'. It was having an empty TeX Information even if I am using MikTeX because I forgot that I have a wrapper script for the kpsewhich command which translates all paths and path lists to posix format ... -- Enrico
Re: LyX on Cygwin
Enrico Forestieri [EMAIL PROTECTED] writes: On Sat, 25 Feb 2006 14:42:04 -0800, Stephen Harris wrote: The other difference is that I have a populated TeX Information and I can send you a screenshot of it present in CygLyxWin140_5. I'm wondering if there are differences due to TeTeX vs. Miktex? No, I don't think that's the problem, it must be something else. I have an empty TeX information with both teTeX and MikTeX, and with both 1.3.7 and 1.4.0 but LyX works and so I don't care... it must be something with my environment. I found what the problem is. In the file scripts/TeXFiles.sh it is assumed that the path separator is ';' when it detects a Windows environment. Now, in cygwin the path separator is ':', instead, and that causes the empty TeX Information dialog. This is only a problem with the cygwin tetex as MikTeX always returns Windows style path lists separated by ';'. It was having an empty TeX Information even if I am using MikTeX because I forgot that I have a wrapper script for the kpsewhich command which translates all paths and path lists to posix format ... -- Enrico
Re: LyX on Cygwin
Enrico Forestieri <[EMAIL PROTECTED]> writes: > > On Sat, 25 Feb 2006 14:42:04 -0800, Stephen Harris wrote: > > > The other difference is that I have a populated TeX Information > > and I can send you a screenshot of it present in CygLyxWin140_5. > > I'm wondering if there are differences due to TeTeX vs. Miktex? > > No, I don't think that's the problem, it must be something else. > I have an empty TeX information with both teTeX and MikTeX, and with > both 1.3.7 and 1.4.0 but LyX works and so I don't care... it must be > something with my environment. I found what the problem is. In the file scripts/TeXFiles.sh it is assumed that the path separator is ';' when it detects a Windows environment. Now, in cygwin the path separator is ':', instead, and that causes the empty "TeX Information" dialog. This is only a problem with the cygwin tetex as MikTeX always returns Windows style path lists separated by ';'. It was having an empty "TeX Information" even if I am using MikTeX because I forgot that I have a wrapper script for the kpsewhich command which translates all paths and path lists to posix format ... -- Enrico
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: lyx-users@lists.lyx.org Sent: Friday, February 24, 2006 4:33 PM Subject: Re: LyX on Cygwin On Fri, 24 Feb 2006 14:13:04 -0800, Stephen Harris wrote: The Tex Information produces a window but it contains no information. Yes, I also see this, but then this also happens with 1.3.7. The good new is that I found the apparent problem. I had tetex-base installed for Cygwin. I uninstalled and Reconfigured and I got all my Viewers displayed. Also Tex Information is populated. I used mount -f C: /c (not mount -f C: /cygdrive/c ?) as advised. My favorite test file, sample.lyx, does convert eps and jpeg, I think that you have a working copy of LyX. You should simply fix some glitches. -- Enrico I am unable to convert sample.lyx into DVI or dvipdfm which I can do in 137 but not in LyX140_pre3 compiled with Mingw. I did see why Georg thought this was a .bb error, but I copied the *.bb to the /c/cygwin/tmp directory after renaming the original .bb files to the ones Cygwin was complaining about not finding. That doesn't work. So this seems to be a LyX140 problem. Working pretty good, Stephen
Re: LyX on Cygwin
On Fri, 24 Feb 2006 19:52:13 -0800, Stephen Harris wrote: [...] The Tex Information produces a window but it contains no information. Yes, I also see this, but then this also happens with 1.3.7. Perhaps normal for Cygwin/Linux but you can see all these files and their paths with Uwe or Angus native LyXwin. Or with Mingw build of LyX1.4.0_pre3. It is how I used to check that LyX communicated with Miktex:texmf Really? It is empty for me with those versions, too, but LyX works perfectly. I used mount -f C: /c (not mount -f C: /cygdrive/c ?) as advised. Correct. To see if that works try ls /c in a cygwin shell. Yes I see lots of my stuff. When I use File-Open it still displays the path in terms of /cygdrive/c/ which makes me nervous. That's strange, indeed. I get /cygdrive/c converted to /c when I type it in the text input area in File-Open. Try the following command and see what output it gives: cygpath 'C:\somepath' Does it says /cygdrive/c/somepath or /c/somepath? [...] The Working directory automatically generated by LyX is C:/Cygwin/.xemacs Uh? It seems that you have not set the HOME variable. LyX/Cygwin uses HOME instead of USERPROFILE. Perhaps I should patch the sources such that USERPROFILE is used as a fallback if HOME is not set. For the moment, you can fix this by adding the HOME var in the same way you add the PATH var but in the user section. Set HOME to a folder of your choice and then try launching LyX with the option -dbg init to see what it thinks your home_dir is. I used to have Xemacs for Cygwin installed. I set the HOME variable to C:\Cygwin\.xemacs for it. I now have another version of Xemacs set to HOME there also so if I change it I have to move init.el files etc. Ok, you set it that way. No need to change it. [...] As I noted above, always use posix syntax in path_prefix, so write that as /c/texmf/miktex/bin:/c/reader7/etc The ':' char must only be used as a separator. Please try the following as path_prefix (I am assuming that your AcroRd32.exe is in C:\reader7\Reader\acrord32 and that you issued the mount -f C: /c command) /usr/local/bin:/usr/bin:/usr/X11R6/bin:/c/texmf/miktex/bin:/c/reader7/Reader/ac ord32 Oops. No acrord32 is short for the acrord32.exe I just noticed this after trying it and it failed. So I tried :/c/reader7/Reader/ which didn't work. I just tried it without the trailing slash /, and it didn't work. oh... Remember that only directories should be listed in path_prefix. I start LyX with an icon linked to C:\cygwin\usr\local\bin\LyX-1.4.0.exe and it gives me an error message Locale en_US could not be set which has never mattered in the past. My language is set to English in LyX. The Locale error follows after the LyX will not be able to produce output. Yes, this is normal. For some reason en_US is not present in cygwin. [...] I've watched Reconfigure process. It says yes to finding pdflatex and acrord32 and gsview32. I don't have any Viewers, no DVI or Postscript. I added :/c/gs/gs8.51/bin:/c/ghostgum/gsview to Path prefix and turned on Instant Preview. No previewers. Before when I had this problem I ran sh configure from lyx/resources/lyx I'll give that -dbg init a try before closing. yes my hom_dir is .xemacs ctrl-d applied to splash.lyx says No information for exporting the format DVI. Something is causing that 'missing TeX class article -dbg init partial output [I tried exporting from the LyX command line.] No information for exporting the format DVI. Error: Couldn't export file No information for exporting the format DVI. Error: Couldn't export file No information for exporting the format LaTeX. sh: -c: line 0: syntax error near unexpected token `' sh: -c: line 0: `( /c/texmf/miktex/bin/latex.exe ) ' Error: Couldn't export file Hmmm... I really have no clue to it... -- Enrico
Re: LyX on Cygwin
On Sat, 25 Feb 2006 04:07:54 -0800, Stephen Harris wrote: On Fri, 24 Feb 2006 14:13:04 -0800, Stephen Harris wrote: The Tex Information produces a window but it contains no information. Yes, I also see this, but then this also happens with 1.3.7. The good new is that I found the apparent problem. I had tetex-base installed for Cygwin. I uninstalled and Reconfigured and I got all my Viewers displayed. Also Tex Information is populated. I am quite suprprised that it doesn't seem to work with the cygwin tetex. I also have MikTeX so I didn't noticed it. However, in Tools-preferences you will find an extra tab Outputs-Paths which is not present in a non-cygwin build. Try unchecking Use Cygwin-style paths and see what happens. I think that LyX is doing strange things as checking it seems to produce non-cygwin-style paths while unchecking it, the paths seem to be in cygwin-style. The logic seems to be reversed and it is really confusing. I used mount -f C: /c (not mount -f C: /cygdrive/c ?) as advised. My favorite test file, sample.lyx, does convert eps and jpeg, I think that you have a working copy of LyX. You should simply fix some glitches. -- Enrico I am unable to convert sample.lyx into DVI or dvipdfm which I can do in 137 but not in LyX140_pre3 compiled with Mingw. I can do both with both a mingw and cygwin build, so it must be something with your configuration. I did see why Georg thought this was a .bb error, but I copied the *.bb to the /c/cygwin/tmp directory after renaming the original .bb files to the ones Cygwin was complaining about not finding. That doesn't work. So this seems to be a LyX140 problem. Sorry, I don't follow you here. -- Enrico
Re: LyX on Cygwin
Enrico Forestieri [EMAIL PROTECTED] writes: On Sat, 25 Feb 2006 04:07:54 -0800, Stephen Harris wrote: On Fri, 24 Feb 2006 14:13:04 -0800, Stephen Harris wrote: The Tex Information produces a window but it contains no information. Yes, I also see this, but then this also happens with 1.3.7. The good new is that I found the apparent problem. I had tetex-base installed for Cygwin. I uninstalled and Reconfigured and I got all my Viewers displayed. Also Tex Information is populated. I am quite suprprised that it doesn't seem to work with the cygwin tetex. I also have MikTeX so I didn't noticed it. However, in Tools-preferences you will find an extra tab Outputs-Paths which is not present in a non-cygwin build. Try unchecking Use Cygwin-style paths and see what happens. I think that LyX is doing strange things as checking it seems to produce non-cygwin-style paths while unchecking it, the paths seem to be in cygwin-style. The logic seems to be reversed and it is really confusing. I tried installing the tetex-base, tetex-bin, and tetex-extra cygwin packages, reconfigured LyX and everything seems to work as usual. I did not even had to touch the Use Cygwin-style paths check button. I tested almost everything, so I would say that it works for me. -- Enrico
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: lyx-users@lists.lyx.org Sent: Saturday, February 25, 2006 9:46 AM Subject: Re: LyX on Cygwin Enrico Forestieri [EMAIL PROTECTED] writes: On Sat, 25 Feb 2006 04:07:54 -0800, Stephen Harris wrote: On Fri, 24 Feb 2006 14:13:04 -0800, Stephen Harris wrote: The Tex Information produces a window but it contains no information. Yes, I also see this, but then this also happens with 1.3.7. The good new is that I found the apparent problem. I had tetex-base installed for Cygwin. I uninstalled and Reconfigured and I got all my Viewers displayed. Also Tex Information is populated. I am quite suprprised that it doesn't seem to work with the cygwin tetex. I also have MikTeX so I didn't noticed it. However, in Tools-preferences you will find an extra tab Outputs-Paths which is not present in a non-cygwin build. Try unchecking Use Cygwin-style paths and see what happens. I think that LyX is doing strange things as checking it seems to produce non-cygwin-style paths while unchecking it, the paths seem to be in cygwin-style. The logic seems to be reversed and it is really confusing. I tried installing the tetex-base, tetex-bin, and tetex-extra cygwin packages, reconfigured LyX and everything seems to work as usual. I did not even had to touch the Use Cygwin-style paths check button. I tested almost everything, so I would say that it works for me. -- Enrico Yes I see lots of my stuff. When I use File-Open it still displays the path in terms of /cygdrive/c/ which makes me nervous. EF: That's strange, indeed. I get /cygdrive/c converted to /c when I type it in the text input area in File-Open. Try the following command and see what output it gives: cygpath 'C:\somepath' Does it says /cygdrive/c/somepath or /c/somepath? [EMAIL PROTECTED] /c $ cygpath c:\xemtex c:xemtex [EMAIL PROTECTED] /c $ cygpath c:\xemtex\XemacsBak c:xemtexXemacsBak No slashes, no delimiter. -- I am unable to convert sample.lyx into DVI or dvipdfm which I can do in 137 but not in LyX140_pre3 compiled with Mingw. I can do both with both a mingw and cygwin build, so it must be something with your configuration. I did see why Georg thought this was a .bb error, but I copied the *.bb to the /c/cygwin/tmp directory after renaming the original .bb files to the ones Cygwin was complaining about not finding. That doesn't work. So this seems to be a LyX140 problem. SH: The file is sample.tex found in C:\texmf\doc\dvipdfm (imported to LyX) Maybe it is this particular file (not in general) but I can view the graphics within LyX and convert to DVI with NativeWinLyX137 but not LyX140_3 or _5 These are the error messages produced by the attempted DVI conversion: LaTeX Error: File '0_cygdrive_c_texmf_doc_dvipdfm_mwicks.bb not found LaTeX Error: File '1_cygdrive_c_texmf_doc_dvipdfm_transistor not found I reported this on bugzilla as bug 2299. http://bugzilla.lyx.org/show_bug.cgi?id=2299 Georg Baum wrote #7: I can reproduce the problem with your file (after getting the images from the dvipdfm distribution), and I also know the cause: dvipdfm needs .bb files for all graphics. LyX simply does not know that and does not copy these files to the temporary directory where latex and dvipdfm are run. This means that LyX 1.4 is currently not able to produce pdf via dvipdfm if the file contains graphics. LyX 1.3.x should have the same problem if you are using a temporary directory. I'll try to fix this for 1.4.1 (or maybe 1.4.1 if it turns out to be unexpectedly difficult). end of quote I unchecked 'use Cygwin paths' and couldn't tell any difference in regard to converting to DVI (or checked for that matter). I have /c/texmf/miktex/bin in Path prefix as instructed, maybe you don't? I also put /c/ImageMagick in Path prefix because I think the Cygwin ImageMagick might interfere similar to texmf, and because it is consistent. There seem to be two differences, maybe due to configuration? Maybe you could test sample.tex imported to LyX sample.lyx? C:\texmf\doc\dvipdfm\sample.tex See if dvipdfm and DVI still work for you or if it is the file itself. The other difference is that I have a populated TeX Information and I can send you a screenshot of it present in CygLyxWin140_5. I'm wondering if there are differences due to TeTeX vs. Miktex? OTOH, if you are tired of this issue, the build is fine, thanks to you. I've tried to consolidate our recent posts into this one. Regards, Stephen
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: lyx-users@lists.lyx.org Sent: Saturday, February 25, 2006 9:46 AM Subject: Re: LyX on Cygwin Enrico Forestieri [EMAIL PROTECTED] writes: I tried installing the tetex-base, tetex-bin, and tetex-extra cygwin packages, reconfigured LyX and everything seems to work as usual. I did not even had to touch the Use Cygwin-style paths check button. I tested almost everything, so I would say that it works for me. -- Enrico I reinstalled all the tetex packages and it reproduced the The document uses a missing TeX class article. error message. It did display the TeX Information files and paths. I think it was using the previously generated information made when there was no error message. I uninstalled the tetex packages and it now works with or without /c/texmf/miktex/bin in the Path prefix statement. Use cygwin-style paths remained on throughout this.
Re: LyX on Cygwin
On Sat, 25 Feb 2006 14:42:04 -0800, Stephen Harris wrote: [...] Yes I see lots of my stuff. When I use File-Open it still displays the path in terms of /cygdrive/c/ which makes me nervous. EF: That's strange, indeed. I get /cygdrive/c converted to /c when I type it in the text input area in File-Open. Try the following command and see what output it gives: cygpath 'C:\somepath' Does it says /cygdrive/c/somepath or /c/somepath? [EMAIL PROTECTED] /c $ cygpath c:\xemtex c:xemtex [EMAIL PROTECTED] /c $ cygpath c:\xemtex\XemacsBak c:xemtexXemacsBak No slashes, no delimiter. You forgot the single quotes. In *nix shells the backslash \ is used for quoting the next character, so you have to write it two times or put the path in single (not double) quotes. So, you should write: cygpath 'C:\somepath' or cygpath C:\\somepath The \ can also be used to quote spaces: 'C:\some path with spaces' is as good as C:\\some\ path\ with\ spaces -- I am unable to convert sample.lyx into DVI or dvipdfm which I can do in 137 but not in LyX140_pre3 compiled with Mingw. I can do both with both a mingw and cygwin build, so it must be something with your configuration. I did see why Georg thought this was a .bb error, but I copied the *.bb to the /c/cygwin/tmp directory after renaming the original .bb files to the ones Cygwin was complaining about not finding. That doesn't work. So this seems to be a LyX140 problem. SH: The file is sample.tex found in C:\texmf\doc\dvipdfm (imported to LyX) Maybe it is this particular file (not in general) but I can view the graphics within LyX and convert to DVI with NativeWinLyX137 but not LyX140_3 or _5 These are the error messages produced by the attempted DVI conversion: LaTeX Error: File '0_cygdrive_c_texmf_doc_dvipdfm_mwicks.bb not found LaTeX Error: File '1_cygdrive_c_texmf_doc_dvipdfm_transistor not found I reported this on bugzilla as bug 2299. http://bugzilla.lyx.org/show_bug.cgi?id=2299 Georg Baum wrote #7: I can reproduce the problem with your file (after getting the images from the dvipdfm distribution), and I also know the cause: dvipdfm needs .bb files for all graphics. LyX simply does not know that and does not copy these files to the temporary directory where latex and dvipdfm are run. This means that LyX 1.4 is currently not able to produce pdf via dvipdfm if the file contains graphics. LyX 1.3.x should have the same problem if you are using a temporary directory. I'll try to fix this for 1.4.1 (or maybe 1.4.1 if it turns out to be unexpectedly difficult). end of quote I unchecked 'use Cygwin paths' and couldn't tell any difference in regard to converting to DVI (or checked for that matter). I have /c/texmf/miktex/bin in Path prefix as instructed, maybe you don't? I also put /c/ImageMagick in Path prefix because I think the Cygwin ImageMagick might interfere similar to texmf, and because it is consistent. I think it is safe to put every needed path in path_prefix. I once was concerned about this because I believed that the overall PATH length would have grown despite the fact I already had something in the system PATH. But after having a look at the LyX sources, I saw that it is done in a clever way: if something is already in the system PATH it is not added. So, if you already have an entry in the system PATH, you don't need to put it in path_prefix, but if you put something in path_prefix and it is already in the system PATH, this entry is not duplicated. There seem to be two differences, maybe due to configuration? Maybe you could test sample.tex imported to LyX sample.lyx? C:\texmf\doc\dvipdfm\sample.tex See if dvipdfm and DVI still work for you or if it is the file itself. I think that Georg is correct. After copying the .bb files to the temporary directory, dvipdfm worked, but I had also to copy there the pdf versions... it seems that LyX fails to recognize that it should convert the eps files to pdf format. No way as regards DVI output, but then I think that that is a dvipdfm specific file. All is ok with 1.3.7. The other difference is that I have a populated TeX Information and I can send you a screenshot of it present in CygLyxWin140_5. I'm wondering if there are differences due to TeTeX vs. Miktex? No, I don't think that's the problem, it must be something else. I have an empty TeX information with both teTeX and MikTeX, and with both 1.3.7 and 1.4.0 but LyX works and so I don't care... it must be something with my environment. OTOH, if you are tired of this issue, the build is fine, thanks to you. I've tried to consolidate our recent posts into this one. You're welcome. -- Enrico
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: lyx-users@lists.lyx.org Sent: Saturday, February 25, 2006 6:04 PM Subject: Re: LyX on Cygwin On Sat, 25 Feb 2006 14:42:04 -0800, Stephen Harris wrote: [EMAIL PROTECTED] /c $ cygpath c:\xemtex c:xemtex [EMAIL PROTECTED] /c $ cygpath c:\xemtex\XemacsBak c:xemtexXemacsBak No slashes, no delimiter. You forgot the single quotes. In *nix shells the backslash \ is used for quoting the next character, so you have to write it two times or put the path in single (not double) quotes. So, you should write: cygpath 'C:\somepath' or cygpath C:\\somepath The \ can also be used to quote spaces: 'C:\some path with spaces' is as good as C:\\some\ path\ with\ spaces Yes, cygpath 'C:\somepath' produced /c/xemtex. On my system the .eps files do get converted to .pdf 02/25/2006 07:33 PM 10,020 1_cygdrive_c_texmf_doc_dvipdfm_transistor.eps 02/25/2006 07:34 PM 2,360 1_cygdrive_c_texmf_doc_dvipdfm_transistor.pdf 02/25/2006 07:33 PM 7,215 2_cygdrive_c_texmf_doc_dvipdfm_something.eps 02/25/2006 07:34 PM 3,284 2_cygdrive_c_texmf_doc_dvipdfm_something.pdf LyX137 converts something.eps and transistor.eps to something.pdf transistor.pdf But these smaller .pdfs don't get included in the large .pdf which has the text in 140 No use to beat a dead horse anymore, I'll find a new one :-) Stephen
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: lyx-users@lists.lyx.org Sent: Friday, February 24, 2006 4:33 PM Subject: Re: LyX on Cygwin On Fri, 24 Feb 2006 14:13:04 -0800, Stephen Harris wrote: The Tex Information produces a window but it contains no information. Yes, I also see this, but then this also happens with 1.3.7. The good new is that I found the apparent problem. I had tetex-base installed for Cygwin. I uninstalled and Reconfigured and I got all my Viewers displayed. Also Tex Information is populated. I used mount -f C: /c (not mount -f C: /cygdrive/c ?) as advised. My favorite test file, sample.lyx, does convert eps and jpeg, I think that you have a working copy of LyX. You should simply fix some glitches. -- Enrico I am unable to convert sample.lyx into DVI or dvipdfm which I can do in 137 but not in LyX140_pre3 compiled with Mingw. I did see why Georg thought this was a .bb error, but I copied the *.bb to the /c/cygwin/tmp directory after renaming the original .bb files to the ones Cygwin was complaining about not finding. That doesn't work. So this seems to be a LyX140 problem. Working pretty good, Stephen
Re: LyX on Cygwin
On Fri, 24 Feb 2006 19:52:13 -0800, Stephen Harris wrote: [...] The Tex Information produces a window but it contains no information. Yes, I also see this, but then this also happens with 1.3.7. Perhaps normal for Cygwin/Linux but you can see all these files and their paths with Uwe or Angus native LyXwin. Or with Mingw build of LyX1.4.0_pre3. It is how I used to check that LyX communicated with Miktex:texmf Really? It is empty for me with those versions, too, but LyX works perfectly. I used mount -f C: /c (not mount -f C: /cygdrive/c ?) as advised. Correct. To see if that works try ls /c in a cygwin shell. Yes I see lots of my stuff. When I use File-Open it still displays the path in terms of /cygdrive/c/ which makes me nervous. That's strange, indeed. I get /cygdrive/c converted to /c when I type it in the text input area in File-Open. Try the following command and see what output it gives: cygpath 'C:\somepath' Does it says /cygdrive/c/somepath or /c/somepath? [...] The Working directory automatically generated by LyX is C:/Cygwin/.xemacs Uh? It seems that you have not set the HOME variable. LyX/Cygwin uses HOME instead of USERPROFILE. Perhaps I should patch the sources such that USERPROFILE is used as a fallback if HOME is not set. For the moment, you can fix this by adding the HOME var in the same way you add the PATH var but in the user section. Set HOME to a folder of your choice and then try launching LyX with the option -dbg init to see what it thinks your home_dir is. I used to have Xemacs for Cygwin installed. I set the HOME variable to C:\Cygwin\.xemacs for it. I now have another version of Xemacs set to HOME there also so if I change it I have to move init.el files etc. Ok, you set it that way. No need to change it. [...] As I noted above, always use posix syntax in path_prefix, so write that as /c/texmf/miktex/bin:/c/reader7/etc The ':' char must only be used as a separator. Please try the following as path_prefix (I am assuming that your AcroRd32.exe is in C:\reader7\Reader\acrord32 and that you issued the mount -f C: /c command) /usr/local/bin:/usr/bin:/usr/X11R6/bin:/c/texmf/miktex/bin:/c/reader7/Reader/ac ord32 Oops. No acrord32 is short for the acrord32.exe I just noticed this after trying it and it failed. So I tried :/c/reader7/Reader/ which didn't work. I just tried it without the trailing slash /, and it didn't work. oh... Remember that only directories should be listed in path_prefix. I start LyX with an icon linked to C:\cygwin\usr\local\bin\LyX-1.4.0.exe and it gives me an error message Locale en_US could not be set which has never mattered in the past. My language is set to English in LyX. The Locale error follows after the LyX will not be able to produce output. Yes, this is normal. For some reason en_US is not present in cygwin. [...] I've watched Reconfigure process. It says yes to finding pdflatex and acrord32 and gsview32. I don't have any Viewers, no DVI or Postscript. I added :/c/gs/gs8.51/bin:/c/ghostgum/gsview to Path prefix and turned on Instant Preview. No previewers. Before when I had this problem I ran sh configure from lyx/resources/lyx I'll give that -dbg init a try before closing. yes my hom_dir is .xemacs ctrl-d applied to splash.lyx says No information for exporting the format DVI. Something is causing that 'missing TeX class article -dbg init partial output [I tried exporting from the LyX command line.] No information for exporting the format DVI. Error: Couldn't export file No information for exporting the format DVI. Error: Couldn't export file No information for exporting the format LaTeX. sh: -c: line 0: syntax error near unexpected token `' sh: -c: line 0: `( /c/texmf/miktex/bin/latex.exe ) ' Error: Couldn't export file Hmmm... I really have no clue to it... -- Enrico
Re: LyX on Cygwin
On Sat, 25 Feb 2006 04:07:54 -0800, Stephen Harris wrote: On Fri, 24 Feb 2006 14:13:04 -0800, Stephen Harris wrote: The Tex Information produces a window but it contains no information. Yes, I also see this, but then this also happens with 1.3.7. The good new is that I found the apparent problem. I had tetex-base installed for Cygwin. I uninstalled and Reconfigured and I got all my Viewers displayed. Also Tex Information is populated. I am quite suprprised that it doesn't seem to work with the cygwin tetex. I also have MikTeX so I didn't noticed it. However, in Tools-preferences you will find an extra tab Outputs-Paths which is not present in a non-cygwin build. Try unchecking Use Cygwin-style paths and see what happens. I think that LyX is doing strange things as checking it seems to produce non-cygwin-style paths while unchecking it, the paths seem to be in cygwin-style. The logic seems to be reversed and it is really confusing. I used mount -f C: /c (not mount -f C: /cygdrive/c ?) as advised. My favorite test file, sample.lyx, does convert eps and jpeg, I think that you have a working copy of LyX. You should simply fix some glitches. -- Enrico I am unable to convert sample.lyx into DVI or dvipdfm which I can do in 137 but not in LyX140_pre3 compiled with Mingw. I can do both with both a mingw and cygwin build, so it must be something with your configuration. I did see why Georg thought this was a .bb error, but I copied the *.bb to the /c/cygwin/tmp directory after renaming the original .bb files to the ones Cygwin was complaining about not finding. That doesn't work. So this seems to be a LyX140 problem. Sorry, I don't follow you here. -- Enrico
Re: LyX on Cygwin
Enrico Forestieri [EMAIL PROTECTED] writes: On Sat, 25 Feb 2006 04:07:54 -0800, Stephen Harris wrote: On Fri, 24 Feb 2006 14:13:04 -0800, Stephen Harris wrote: The Tex Information produces a window but it contains no information. Yes, I also see this, but then this also happens with 1.3.7. The good new is that I found the apparent problem. I had tetex-base installed for Cygwin. I uninstalled and Reconfigured and I got all my Viewers displayed. Also Tex Information is populated. I am quite suprprised that it doesn't seem to work with the cygwin tetex. I also have MikTeX so I didn't noticed it. However, in Tools-preferences you will find an extra tab Outputs-Paths which is not present in a non-cygwin build. Try unchecking Use Cygwin-style paths and see what happens. I think that LyX is doing strange things as checking it seems to produce non-cygwin-style paths while unchecking it, the paths seem to be in cygwin-style. The logic seems to be reversed and it is really confusing. I tried installing the tetex-base, tetex-bin, and tetex-extra cygwin packages, reconfigured LyX and everything seems to work as usual. I did not even had to touch the Use Cygwin-style paths check button. I tested almost everything, so I would say that it works for me. -- Enrico
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: lyx-users@lists.lyx.org Sent: Saturday, February 25, 2006 9:46 AM Subject: Re: LyX on Cygwin Enrico Forestieri [EMAIL PROTECTED] writes: On Sat, 25 Feb 2006 04:07:54 -0800, Stephen Harris wrote: On Fri, 24 Feb 2006 14:13:04 -0800, Stephen Harris wrote: The Tex Information produces a window but it contains no information. Yes, I also see this, but then this also happens with 1.3.7. The good new is that I found the apparent problem. I had tetex-base installed for Cygwin. I uninstalled and Reconfigured and I got all my Viewers displayed. Also Tex Information is populated. I am quite suprprised that it doesn't seem to work with the cygwin tetex. I also have MikTeX so I didn't noticed it. However, in Tools-preferences you will find an extra tab Outputs-Paths which is not present in a non-cygwin build. Try unchecking Use Cygwin-style paths and see what happens. I think that LyX is doing strange things as checking it seems to produce non-cygwin-style paths while unchecking it, the paths seem to be in cygwin-style. The logic seems to be reversed and it is really confusing. I tried installing the tetex-base, tetex-bin, and tetex-extra cygwin packages, reconfigured LyX and everything seems to work as usual. I did not even had to touch the Use Cygwin-style paths check button. I tested almost everything, so I would say that it works for me. -- Enrico Yes I see lots of my stuff. When I use File-Open it still displays the path in terms of /cygdrive/c/ which makes me nervous. EF: That's strange, indeed. I get /cygdrive/c converted to /c when I type it in the text input area in File-Open. Try the following command and see what output it gives: cygpath 'C:\somepath' Does it says /cygdrive/c/somepath or /c/somepath? [EMAIL PROTECTED] /c $ cygpath c:\xemtex c:xemtex [EMAIL PROTECTED] /c $ cygpath c:\xemtex\XemacsBak c:xemtexXemacsBak No slashes, no delimiter. -- I am unable to convert sample.lyx into DVI or dvipdfm which I can do in 137 but not in LyX140_pre3 compiled with Mingw. I can do both with both a mingw and cygwin build, so it must be something with your configuration. I did see why Georg thought this was a .bb error, but I copied the *.bb to the /c/cygwin/tmp directory after renaming the original .bb files to the ones Cygwin was complaining about not finding. That doesn't work. So this seems to be a LyX140 problem. SH: The file is sample.tex found in C:\texmf\doc\dvipdfm (imported to LyX) Maybe it is this particular file (not in general) but I can view the graphics within LyX and convert to DVI with NativeWinLyX137 but not LyX140_3 or _5 These are the error messages produced by the attempted DVI conversion: LaTeX Error: File '0_cygdrive_c_texmf_doc_dvipdfm_mwicks.bb not found LaTeX Error: File '1_cygdrive_c_texmf_doc_dvipdfm_transistor not found I reported this on bugzilla as bug 2299. http://bugzilla.lyx.org/show_bug.cgi?id=2299 Georg Baum wrote #7: I can reproduce the problem with your file (after getting the images from the dvipdfm distribution), and I also know the cause: dvipdfm needs .bb files for all graphics. LyX simply does not know that and does not copy these files to the temporary directory where latex and dvipdfm are run. This means that LyX 1.4 is currently not able to produce pdf via dvipdfm if the file contains graphics. LyX 1.3.x should have the same problem if you are using a temporary directory. I'll try to fix this for 1.4.1 (or maybe 1.4.1 if it turns out to be unexpectedly difficult). end of quote I unchecked 'use Cygwin paths' and couldn't tell any difference in regard to converting to DVI (or checked for that matter). I have /c/texmf/miktex/bin in Path prefix as instructed, maybe you don't? I also put /c/ImageMagick in Path prefix because I think the Cygwin ImageMagick might interfere similar to texmf, and because it is consistent. There seem to be two differences, maybe due to configuration? Maybe you could test sample.tex imported to LyX sample.lyx? C:\texmf\doc\dvipdfm\sample.tex See if dvipdfm and DVI still work for you or if it is the file itself. The other difference is that I have a populated TeX Information and I can send you a screenshot of it present in CygLyxWin140_5. I'm wondering if there are differences due to TeTeX vs. Miktex? OTOH, if you are tired of this issue, the build is fine, thanks to you. I've tried to consolidate our recent posts into this one. Regards, Stephen
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: lyx-users@lists.lyx.org Sent: Saturday, February 25, 2006 9:46 AM Subject: Re: LyX on Cygwin Enrico Forestieri [EMAIL PROTECTED] writes: I tried installing the tetex-base, tetex-bin, and tetex-extra cygwin packages, reconfigured LyX and everything seems to work as usual. I did not even had to touch the Use Cygwin-style paths check button. I tested almost everything, so I would say that it works for me. -- Enrico I reinstalled all the tetex packages and it reproduced the The document uses a missing TeX class article. error message. It did display the TeX Information files and paths. I think it was using the previously generated information made when there was no error message. I uninstalled the tetex packages and it now works with or without /c/texmf/miktex/bin in the Path prefix statement. Use cygwin-style paths remained on throughout this.
Re: LyX on Cygwin
On Sat, 25 Feb 2006 14:42:04 -0800, Stephen Harris wrote: [...] Yes I see lots of my stuff. When I use File-Open it still displays the path in terms of /cygdrive/c/ which makes me nervous. EF: That's strange, indeed. I get /cygdrive/c converted to /c when I type it in the text input area in File-Open. Try the following command and see what output it gives: cygpath 'C:\somepath' Does it says /cygdrive/c/somepath or /c/somepath? [EMAIL PROTECTED] /c $ cygpath c:\xemtex c:xemtex [EMAIL PROTECTED] /c $ cygpath c:\xemtex\XemacsBak c:xemtexXemacsBak No slashes, no delimiter. You forgot the single quotes. In *nix shells the backslash \ is used for quoting the next character, so you have to write it two times or put the path in single (not double) quotes. So, you should write: cygpath 'C:\somepath' or cygpath C:\\somepath The \ can also be used to quote spaces: 'C:\some path with spaces' is as good as C:\\some\ path\ with\ spaces -- I am unable to convert sample.lyx into DVI or dvipdfm which I can do in 137 but not in LyX140_pre3 compiled with Mingw. I can do both with both a mingw and cygwin build, so it must be something with your configuration. I did see why Georg thought this was a .bb error, but I copied the *.bb to the /c/cygwin/tmp directory after renaming the original .bb files to the ones Cygwin was complaining about not finding. That doesn't work. So this seems to be a LyX140 problem. SH: The file is sample.tex found in C:\texmf\doc\dvipdfm (imported to LyX) Maybe it is this particular file (not in general) but I can view the graphics within LyX and convert to DVI with NativeWinLyX137 but not LyX140_3 or _5 These are the error messages produced by the attempted DVI conversion: LaTeX Error: File '0_cygdrive_c_texmf_doc_dvipdfm_mwicks.bb not found LaTeX Error: File '1_cygdrive_c_texmf_doc_dvipdfm_transistor not found I reported this on bugzilla as bug 2299. http://bugzilla.lyx.org/show_bug.cgi?id=2299 Georg Baum wrote #7: I can reproduce the problem with your file (after getting the images from the dvipdfm distribution), and I also know the cause: dvipdfm needs .bb files for all graphics. LyX simply does not know that and does not copy these files to the temporary directory where latex and dvipdfm are run. This means that LyX 1.4 is currently not able to produce pdf via dvipdfm if the file contains graphics. LyX 1.3.x should have the same problem if you are using a temporary directory. I'll try to fix this for 1.4.1 (or maybe 1.4.1 if it turns out to be unexpectedly difficult). end of quote I unchecked 'use Cygwin paths' and couldn't tell any difference in regard to converting to DVI (or checked for that matter). I have /c/texmf/miktex/bin in Path prefix as instructed, maybe you don't? I also put /c/ImageMagick in Path prefix because I think the Cygwin ImageMagick might interfere similar to texmf, and because it is consistent. I think it is safe to put every needed path in path_prefix. I once was concerned about this because I believed that the overall PATH length would have grown despite the fact I already had something in the system PATH. But after having a look at the LyX sources, I saw that it is done in a clever way: if something is already in the system PATH it is not added. So, if you already have an entry in the system PATH, you don't need to put it in path_prefix, but if you put something in path_prefix and it is already in the system PATH, this entry is not duplicated. There seem to be two differences, maybe due to configuration? Maybe you could test sample.tex imported to LyX sample.lyx? C:\texmf\doc\dvipdfm\sample.tex See if dvipdfm and DVI still work for you or if it is the file itself. I think that Georg is correct. After copying the .bb files to the temporary directory, dvipdfm worked, but I had also to copy there the pdf versions... it seems that LyX fails to recognize that it should convert the eps files to pdf format. No way as regards DVI output, but then I think that that is a dvipdfm specific file. All is ok with 1.3.7. The other difference is that I have a populated TeX Information and I can send you a screenshot of it present in CygLyxWin140_5. I'm wondering if there are differences due to TeTeX vs. Miktex? No, I don't think that's the problem, it must be something else. I have an empty TeX information with both teTeX and MikTeX, and with both 1.3.7 and 1.4.0 but LyX works and so I don't care... it must be something with my environment. OTOH, if you are tired of this issue, the build is fine, thanks to you. I've tried to consolidate our recent posts into this one. You're welcome. -- Enrico
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: lyx-users@lists.lyx.org Sent: Saturday, February 25, 2006 6:04 PM Subject: Re: LyX on Cygwin On Sat, 25 Feb 2006 14:42:04 -0800, Stephen Harris wrote: [EMAIL PROTECTED] /c $ cygpath c:\xemtex c:xemtex [EMAIL PROTECTED] /c $ cygpath c:\xemtex\XemacsBak c:xemtexXemacsBak No slashes, no delimiter. You forgot the single quotes. In *nix shells the backslash \ is used for quoting the next character, so you have to write it two times or put the path in single (not double) quotes. So, you should write: cygpath 'C:\somepath' or cygpath C:\\somepath The \ can also be used to quote spaces: 'C:\some path with spaces' is as good as C:\\some\ path\ with\ spaces Yes, cygpath 'C:\somepath' produced /c/xemtex. On my system the .eps files do get converted to .pdf 02/25/2006 07:33 PM 10,020 1_cygdrive_c_texmf_doc_dvipdfm_transistor.eps 02/25/2006 07:34 PM 2,360 1_cygdrive_c_texmf_doc_dvipdfm_transistor.pdf 02/25/2006 07:33 PM 7,215 2_cygdrive_c_texmf_doc_dvipdfm_something.eps 02/25/2006 07:34 PM 3,284 2_cygdrive_c_texmf_doc_dvipdfm_something.pdf LyX137 converts something.eps and transistor.eps to something.pdf transistor.pdf But these smaller .pdfs don't get included in the large .pdf which has the text in 140 No use to beat a dead horse anymore, I'll find a new one :-) Stephen
Re: LyX on Cygwin
- Original Message - From: "Enrico Forestieri" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <lyx-users@lists.lyx.org> Sent: Friday, February 24, 2006 4:33 PM Subject: Re: LyX on Cygwin On Fri, 24 Feb 2006 14:13:04 -0800, Stephen Harris wrote: The Tex Information produces a window but it contains no information. Yes, I also see this, but then this also happens with 1.3.7. The good new is that I found the apparent problem. I had tetex-base installed for Cygwin. I uninstalled and Reconfigured and I got all my Viewers displayed. Also Tex Information is populated. I used mount -f C: /c (not mount -f C: /cygdrive/c ?) as advised. My favorite test file, sample.lyx, does convert eps and jpeg, I think that you have a working copy of LyX. You should simply fix some glitches. -- Enrico I am unable to convert sample.lyx into DVI or dvipdfm which I can do in 137 but not in LyX140_pre3 compiled with Mingw. I did see why Georg thought this was a .bb error, but I copied the *.bb to the /c/cygwin/tmp directory after renaming the original .bb files to the ones Cygwin was complaining about not finding. That doesn't work. So this seems to be a LyX140 problem. Working pretty good, Stephen
Re: LyX on Cygwin
On Fri, 24 Feb 2006 19:52:13 -0800, Stephen Harris wrote: [...] >>> The Tex Information produces a >>> window but it contains no information. >> >> Yes, I also see this, but then this also happens with 1.3.7. >> > > Perhaps normal for Cygwin/Linux but you can see all these > files and their paths with Uwe or Angus native LyXwin. Or > with Mingw build of LyX1.4.0_pre3. It is how I used to check > that LyX communicated with Miktex:texmf Really? It is empty for me with those versions, too, but LyX works perfectly. >>> I used mount -f C: /c (not mount -f C: /cygdrive/c ?) as advised. >> >> Correct. To see if that works try "ls /c" in a cygwin shell. >> > > Yes I see lots of my stuff. When I use File->Open it still > displays the path in terms of /cygdrive/c/ which makes me nervous. That's strange, indeed. I get "/cygdrive/c" converted to "/c" when I type it in the text input area in File->Open. Try the following command and see what output it gives: cygpath 'C:\somepath' Does it says "/cygdrive/c/somepath" or "/c/somepath"? [...] >>> The Working directory automatically generated by LyX is >>> C:/Cygwin/.xemacs >> >> Uh? It seems that you have not set the HOME variable. LyX/Cygwin uses >> HOME instead of USERPROFILE. Perhaps I should patch the sources such >> that USERPROFILE is used as a fallback if HOME is not set. >> For the moment, you can fix this by adding the HOME var in the same >> way you add the PATH var but in the user section. Set HOME to a folder >> of your choice and then try launching LyX with the option "-dbg init" >> to see what it thinks your home_dir is. >> > > I used to have Xemacs for Cygwin installed. I set the HOME variable > to C:\Cygwin\.xemacs for it. I now have another version of Xemacs set > to HOME there also so if I change it I have to move init.el files etc. Ok, you set it that way. No need to change it. [...] >> As I noted above, always use posix syntax in path_prefix, so >> write that as /c/texmf/miktex/bin:/c/reader7/etc >> The ':' char must only be used as a separator. >> Please try the following as path_prefix (I am assuming that your >> AcroRd32.exe is in C:\reader7\Reader\acrord32 and that you issued >> the "mount -f C: /c" command) >> >> > /usr/local/bin:/usr/bin:/usr/X11R6/bin:/c/texmf/miktex/bin:/c/reader7/Reader/ac > ord32 >> > > Oops. No acrord32 is short for the acrord32.exe I just noticed this > after trying it and it failed. So I tried :/c/reader7/Reader/ which didn't > work. I just tried it without the trailing slash /, and it didn't work. oh... Remember that only directories should be listed in path_prefix. > I start LyX with an icon linked to C:\cygwin\usr\local\bin\LyX-1.4.0.exe > and it gives me an error message "Locale en_US could not be set" > which has never mattered in the past. My language is set to English in LyX. > The Locale error follows after the "LyX will not be able to produce output." Yes, this is normal. For some reason en_US is not present in cygwin. [...] > I've watched Reconfigure process. It says yes to finding pdflatex > and acrord32 and gsview32. I don't have any Viewers, no DVI or > Postscript. I added :/c/gs/gs8.51/bin:/c/ghostgum/gsview to Path > prefix and turned on Instant Preview. No previewers. Before when > I had this problem I ran sh configure from lyx/resources/lyx I'll > give that -dbg init a try before closing. yes my hom_dir is .xemacs > ctrl-d applied to splash.lyx says "No information for exporting the > format DVI." Something is causing that 'missing TeX class "article" > > -dbg init partial output [I tried exporting from the LyX command line.] > > No information for exporting the format DVI. > Error: Couldn't export file > > No information for exporting the format DVI. > Error: Couldn't export file > > No information for exporting the format LaTeX. > sh: -c: line 0: syntax error near unexpected token `&' > sh: -c: line 0: `( /c/texmf/miktex/bin/latex.exe ) < &' > Error: Couldn't export file > Hmmm... I really have no clue to it... -- Enrico
Re: LyX on Cygwin
On Sat, 25 Feb 2006 04:07:54 -0800, Stephen Harris wrote: > >> On Fri, 24 Feb 2006 14:13:04 -0800, Stephen Harris wrote: >> >>> The Tex Information produces a >>> window but it contains no information. >> >> Yes, I also see this, but then this also happens with 1.3.7. >> > > The good new is that I found the apparent problem. I had tetex-base > installed for Cygwin. I uninstalled and Reconfigured and I got all > my Viewers displayed. Also Tex Information is populated. I am quite suprprised that it doesn't seem to work with the cygwin tetex. I also have MikTeX so I didn't noticed it. However, in Tools->preferences you will find an extra tab Outputs->Paths which is not present in a non-cygwin build. Try unchecking "Use Cygwin-style paths" and see what happens. I think that LyX is doing strange things as checking it seems to produce non-cygwin-style paths while unchecking it, the paths seem to be in cygwin-style. The logic seems to be reversed and it is really confusing. >>> I used mount -f C: /c (not mount -f C: /cygdrive/c ?) as advised. >> >>> My favorite test file, sample.lyx, does convert eps and jpeg, >> >> I think that you have a working copy of LyX. You should simply fix >> some glitches. >> -- Enrico > > I am unable to convert sample.lyx into DVI or dvipdfm which > I can do in 137 but not in LyX140_pre3 compiled with Mingw. I can do both with both a mingw and cygwin build, so it must be something with your configuration. > I did see why Georg thought this was a .bb error, but I copied > the *.bb to the /c/cygwin/tmp directory after renaming the original > .bb files to the ones Cygwin was complaining about not finding. > That doesn't work. So this seems to be a LyX140 problem. Sorry, I don't follow you here. -- Enrico
Re: LyX on Cygwin
Enrico Forestieri <[EMAIL PROTECTED]> writes: > > On Sat, 25 Feb 2006 04:07:54 -0800, Stephen Harris wrote: > > > >> On Fri, 24 Feb 2006 14:13:04 -0800, Stephen Harris wrote: > >> > >>> The Tex Information produces a > >>> window but it contains no information. > >> > >> Yes, I also see this, but then this also happens with 1.3.7. > >> > > > > The good new is that I found the apparent problem. I had tetex-base > > installed for Cygwin. I uninstalled and Reconfigured and I got all > > my Viewers displayed. Also Tex Information is populated. > > I am quite suprprised that it doesn't seem to work with the cygwin tetex. > I also have MikTeX so I didn't noticed it. However, in Tools->preferences > you will find an extra tab Outputs->Paths which is not present in a > non-cygwin build. Try unchecking "Use Cygwin-style paths" and see what > happens. I think that LyX is doing strange things as checking it seems > to produce non-cygwin-style paths while unchecking it, the paths seem to > be in cygwin-style. The logic seems to be reversed and it is really > confusing. I tried installing the tetex-base, tetex-bin, and tetex-extra cygwin packages, reconfigured LyX and everything seems to work as usual. I did not even had to touch the "Use Cygwin-style paths" check button. I tested almost everything, so I would say that it works for me. -- Enrico
Re: LyX on Cygwin
- Original Message - From: "Enrico Forestieri" <[EMAIL PROTECTED]> To: <lyx-users@lists.lyx.org> Sent: Saturday, February 25, 2006 9:46 AM Subject: Re: LyX on Cygwin Enrico Forestieri <[EMAIL PROTECTED]> writes: On Sat, 25 Feb 2006 04:07:54 -0800, Stephen Harris wrote: > >> On Fri, 24 Feb 2006 14:13:04 -0800, Stephen Harris wrote: >> >>> The Tex Information produces a >>> window but it contains no information. >> >> Yes, I also see this, but then this also happens with 1.3.7. >> > > The good new is that I found the apparent problem. I had tetex-base > installed for Cygwin. I uninstalled and Reconfigured and I got all > my Viewers displayed. Also Tex Information is populated. I am quite suprprised that it doesn't seem to work with the cygwin tetex. I also have MikTeX so I didn't noticed it. However, in Tools->preferences you will find an extra tab Outputs->Paths which is not present in a non-cygwin build. Try unchecking "Use Cygwin-style paths" and see what happens. I think that LyX is doing strange things as checking it seems to produce non-cygwin-style paths while unchecking it, the paths seem to be in cygwin-style. The logic seems to be reversed and it is really confusing. I tried installing the tetex-base, tetex-bin, and tetex-extra cygwin packages, reconfigured LyX and everything seems to work as usual. I did not even had to touch the "Use Cygwin-style paths" check button. I tested almost everything, so I would say that it works for me. -- Enrico Yes I see lots of my stuff. When I use File->Open it still displays the path in terms of /cygdrive/c/ which makes me nervous. EF: That's strange, indeed. I get "/cygdrive/c" converted to "/c" when I type it in the text input area in File->Open. Try the following command and see what output it gives: cygpath 'C:\somepath' Does it says "/cygdrive/c/somepath" or "/c/somepath"? [EMAIL PROTECTED] /c $ cygpath c:\xemtex c:xemtex [EMAIL PROTECTED] /c $ cygpath c:\xemtex\XemacsBak c:xemtexXemacsBak No slashes, no delimiter. -- I am unable to convert sample.lyx into DVI or dvipdfm which I can do in 137 but not in LyX140_pre3 compiled with Mingw. I can do both with both a mingw and cygwin build, so it must be something with your configuration. I did see why Georg thought this was a .bb error, but I copied the *.bb to the /c/cygwin/tmp directory after renaming the original .bb files to the ones Cygwin was complaining about not finding. That doesn't work. So this seems to be a LyX140 problem. SH: The file is sample.tex found in C:\texmf\doc\dvipdfm (imported to LyX) Maybe it is this particular file (not in general) but I can view the graphics within LyX and convert to DVI with NativeWinLyX137 but not LyX140_3 or _5 These are the error messages produced by the attempted DVI conversion: LaTeX Error: File '0_cygdrive_c_texmf_doc_dvipdfm_mwicks.bb" not found LaTeX Error: File '1_cygdrive_c_texmf_doc_dvipdfm_transistor" not found I reported this on bugzilla as bug 2299. http://bugzilla.lyx.org/show_bug.cgi?id=2299 Georg Baum wrote #7: "I can reproduce the problem with your file (after getting the images from the dvipdfm distribution), and I also know the cause: dvipdfm needs .bb files for all graphics. LyX simply does not know that and does not copy these files to the temporary directory where latex and dvipdfm are run. This means that LyX 1.4 is currently not able to produce pdf via dvipdfm if the file contains graphics. LyX 1.3.x should have the same problem if you are using a temporary directory. I'll try to fix this for 1.4.1 (or maybe 1.4.1 if it turns out to be unexpectedly difficult)." end of quote I unchecked 'use Cygwin paths' and couldn't tell any difference in regard to converting to DVI (or checked for that matter). I have /c/texmf/miktex/bin in Path prefix as instructed, maybe you don't? I also put /c/ImageMagick in Path prefix because I think the Cygwin ImageMagick might interfere similar to texmf, and because it is consistent. There seem to be two differences, maybe due to configuration? Maybe you could test sample.tex imported to LyX sample.lyx? C:\texmf\doc\dvipdfm\sample.tex See if dvipdfm and DVI still work for you or if it is the file itself. The other difference is that I have a populated TeX Information and I can send you a screenshot of it present in CygLyxWin140_5. I'm wondering if there are differences due to TeTeX vs. Miktex? OTOH, if you are tired of this issue, the build is fine, thanks to you. I've tried to consolidate our recent posts into this one. Regards, Stephen
Re: LyX on Cygwin
- Original Message - From: "Enrico Forestieri" <[EMAIL PROTECTED]> To: <lyx-users@lists.lyx.org> Sent: Saturday, February 25, 2006 9:46 AM Subject: Re: LyX on Cygwin Enrico Forestieri <[EMAIL PROTECTED]> writes: I tried installing the tetex-base, tetex-bin, and tetex-extra cygwin packages, reconfigured LyX and everything seems to work as usual. I did not even had to touch the "Use Cygwin-style paths" check button. I tested almost everything, so I would say that it works for me. -- Enrico I reinstalled all the tetex packages and it reproduced the "The document uses a missing TeX class "article"." error message. It did display the TeX Information files and paths. I think it was using the previously generated information made when there was no error message. I uninstalled the tetex packages and it now works with or without /c/texmf/miktex/bin in the Path prefix statement. Use cygwin-style paths remained on throughout this.
Re: LyX on Cygwin
On Sat, 25 Feb 2006 14:42:04 -0800, Stephen Harris wrote: [...] >> Yes I see lots of my stuff. When I use File->Open it still >> displays the path in terms of /cygdrive/c/ which makes me nervous. > > EF: That's strange, indeed. I get "/cygdrive/c" converted to "/c" when I > type it in the text input area in File->Open. Try the following command > and see what output it gives: > > cygpath 'C:\somepath' > > Does it says "/cygdrive/c/somepath" or "/c/somepath"? > > > [EMAIL PROTECTED] /c > $ cygpath c:\xemtex > c:xemtex > > [EMAIL PROTECTED] /c > $ cygpath c:\xemtex\XemacsBak > c:xemtexXemacsBak > > No slashes, no delimiter. You forgot the single quotes. In *nix shells the backslash \ is used for quoting the next character, so you have to write it two times or put the path in single (not double) quotes. So, you should write: cygpath 'C:\somepath' or cygpath C:\\somepath The \ can also be used to quote spaces: 'C:\some path with spaces' is as good as C:\\some\ path\ with\ spaces > -- > >> I am unable to convert sample.lyx into DVI or dvipdfm which >> I can do in 137 but not in LyX140_pre3 compiled with Mingw. > > I can do both with both a mingw and cygwin build, so it must be > something with your configuration. > >> I did see why Georg thought this was a .bb error, but I copied >> the *.bb to the /c/cygwin/tmp directory after renaming the original >> .bb files to the ones Cygwin was complaining about not finding. >> That doesn't work. So this seems to be a LyX140 problem. > > SH: The file is sample.tex found in C:\texmf\doc\dvipdfm (imported > to LyX) Maybe it is this particular file (not in general) but I can view > the graphics within LyX and convert to DVI with NativeWinLyX137 > but not LyX140_3 or _5 > > These are the error messages produced by the attempted DVI conversion: > LaTeX Error: File '0_cygdrive_c_texmf_doc_dvipdfm_mwicks.bb" not found > LaTeX Error: File '1_cygdrive_c_texmf_doc_dvipdfm_transistor" not found > > I reported this on bugzilla as bug 2299. > http://bugzilla.lyx.org/show_bug.cgi?id=2299 Georg Baum wrote #7: > > "I can reproduce the problem with your file (after getting > the images from the dvipdfm distribution), and I also know > the cause: dvipdfm needs .bb files for all graphics. LyX > simply does not know that and does not copy these files to > the temporary directory where latex and dvipdfm are run. > > This means that LyX 1.4 is currently not able to produce > pdf via dvipdfm if the file contains graphics. LyX 1.3.x > should have the same problem if you are using a temporary > directory. I'll try to fix this for 1.4.1 (or maybe 1.4.1 > if it turns out to be unexpectedly difficult)." end of quote > > > > I unchecked 'use Cygwin paths' and couldn't tell any difference > in regard to converting to DVI (or checked for that matter). > > I have /c/texmf/miktex/bin in Path prefix as instructed, maybe > you don't? I also put /c/ImageMagick in Path prefix because I > think the Cygwin ImageMagick might interfere similar to texmf, > and because it is consistent. I think it is safe to put every needed path in path_prefix. I once was concerned about this because I believed that the overall PATH length would have grown despite the fact I already had something in the system PATH. But after having a look at the LyX sources, I saw that it is done in a clever way: if something is already in the system PATH it is not added. So, if you already have an entry in the system PATH, you don't need to put it in path_prefix, but if you put something in path_prefix and it is already in the system PATH, this entry is not duplicated. > There seem to be two differences, maybe due to configuration? > Maybe you could test sample.tex imported to LyX sample.lyx? > C:\texmf\doc\dvipdfm\sample.tex > See if dvipdfm and DVI still work for you or if it is the file itself. I think that Georg is correct. After copying the .bb files to the temporary directory, dvipdfm worked, but I had also to copy there the pdf versions... it seems that LyX fails to recognize that it should convert the eps files to pdf format. No way as regards DVI output, but then I think that that is a dvipdfm specific file. All is ok with 1.3.7. > The other difference is that I have a populated TeX Information > and I can send you a screenshot of it present in CygLyxWin140_5. > I'm wondering if there are differences due to TeTeX vs. Miktex? No, I don't think that's the problem, it must be something else. I have an empty TeX information with both teTeX and MikTeX, and with both 1.3.7 and 1.4.0 but LyX works and so I don't care... it must be something with my environment. > OTOH, if you are tired of this issue, the build is fine, thanks to you. > I've tried to consolidate our recent posts into this one. You're welcome. --
Re: LyX on Cygwin
- Original Message - From: "Enrico Forestieri" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <lyx-users@lists.lyx.org> Sent: Saturday, February 25, 2006 6:04 PM Subject: Re: LyX on Cygwin On Sat, 25 Feb 2006 14:42:04 -0800, Stephen Harris wrote: [EMAIL PROTECTED] /c $ cygpath c:\xemtex c:xemtex [EMAIL PROTECTED] /c $ cygpath c:\xemtex\XemacsBak c:xemtexXemacsBak No slashes, no delimiter. You forgot the single quotes. In *nix shells the backslash \ is used for quoting the next character, so you have to write it two times or put the path in single (not double) quotes. So, you should write: cygpath 'C:\somepath' or cygpath C:\\somepath The \ can also be used to quote spaces: 'C:\some path with spaces' is as good as C:\\some\ path\ with\ spaces Yes, cygpath 'C:\somepath' produced /c/xemtex. On my system the .eps files do get converted to .pdf 02/25/2006 07:33 PM 10,020 1_cygdrive_c_texmf_doc_dvipdfm_transistor.eps 02/25/2006 07:34 PM 2,360 1_cygdrive_c_texmf_doc_dvipdfm_transistor.pdf 02/25/2006 07:33 PM 7,215 2_cygdrive_c_texmf_doc_dvipdfm_something.eps 02/25/2006 07:34 PM 3,284 2_cygdrive_c_texmf_doc_dvipdfm_something.pdf LyX137 converts something.eps and transistor.eps to something.pdf transistor.pdf But these smaller .pdfs don't get included in the large .pdf which has the text in 140 No use to beat a dead horse anymore, I'll find a new one :-) Stephen
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: lyx-users@lists.lyx.org Sent: Thursday, February 23, 2006 7:52 PM Subject: Re: LyX on Cygwin Stephen Harris [EMAIL PROTECTED] writes: Uh, oh... have you installed the cygwin Qt package by chance? But I do have a .../mkspecs/cygwin-g++-win32/i386pe.x.-no-rdat C:\Cygwin\usr\local\src\qt3\mkspecs That file etc. didn't get copied over to the /lib directory by the script. So I made this .../i386pe.x.-no-rdat conform to the script, but no dice. Copied what I found to where the script said it looked and couldn't find. Well, you should need to do no more and no less than what I put on the wiki, otherwise it means that somenthing is going wrong... Next I notice C:\Cygwin\usr\lib\gcc\i686-pc-cygwin\3.4.4\include\c++\i686-pc-cygwin has no /bin and no ld. It just contains a directory called /bits So I made that conform to the script (mkdir bin and copied /bin files). Run /usr/bin/make confclean; set the Path and Qtdir again; run link_includes; run configure again with all options; edit all: # line; then /usr/bin/make; Returned same error: /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot open linker script file /usr/lib/qt3/mkspecs/cygwin-g++-win32/i386pe.x-no-rdata: No such file or directory collect2: ld returned 1 exit status make[2]: *** [../../bin/moc] Error 1 make[2]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3/src/moc' make[1]: *** [src-moc] Error 2 make[1]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3' I cannot understand from where that prefix /usr/lib/qt3 comes from. If you have installed the official cygwin Qt packages, perhaps this is a symptom of a sort of clashing. -- Enrico [EMAIL PROTECTED] /cygdrive/c/cygwin/usr/local/src/qt3 $ ./configure -platform cygwin-g++-win32 -v -release -static -qt-imgfmt-png etc. So no it is not dynamic, I use this copy and paste every time which is free of typos. But, I do have Qt3-C++/-bin/-devel all installed. I am not sure anymore what is default and what I chose. Seems to me that I also installed some developer tools like bison and flex. So I will uninstall these three Qt3s and see what happens. Nope, didn't work. There was no /usr/lib/qt3 before I recently created it to accomodate the script error report. I found it here: $ sh link_includes link_includes: line 6: cd: /usr/lib/qt3/include: No such file or directory link_includes: line 20: cd: private: No such file or directory ln: creating symbolic link `./q*_p.h' to `../../src/*/q*_p.h': No such file or directory But the current link_includes, cd $QTDIR/include Maybe my environment is screwed up, I'll try printenv(print environment). QTDIR=/usr/lib/qt3 QMAKESPEC=/usr/lib/qt3/mkspecs/cygwin-g++ I changed that to (because that was the configure switch) QMAKESPEC=/usr/local/src/qt3/mkspecs/cygwin-g++-win32 and QTDIR=/usr/local/src/qt3 I used tcsh for setenv QTDIR /usr/local/src/qt3 ? I better check the tcsh Path entry, none, I just added that with bash. The make completed with a few warnings. --- 2. libdir='/usr/local/qt3/src/lib' to libdir='/usr/local/qt-cygwin/lib' Does line 2. have a transposition? should be .../src/qt3 # Directory that this library needs to be installed in: libdir='/cygdrive/c/cygwin/usr/local/src/qt3/lib' I found the above ^^^ and changed it to below, keeping the full path. # Directory that this library needs to be installed in: libdir='/cygdrive/c/cygwin/usr/local/qt-cygwin/lib' -- Finished Qt3 and moving on to LyX 3. Apply the following patch (fixes path_prefix handling): SH: Are the changes supposed to be applied as a manual edit? Regards, Stephen
Re: LyX on Cygwin
Stephen Harris [EMAIL PROTECTED] writes: Stephen at textonyx /cygdrive/c/cygwin/usr/local/src/qt3 $ ./configure -platform cygwin-g++-win32 -v -release -static -qt-imgfmt-png etc. So no it is not dynamic, I use this copy and paste every time which is free of typos. But, I do have Qt3-C++/-bin/-devel all installed. So that's the problem. I investigated a bit and found that qt3-devel is the culprit. It installs the following two files: /etc/profile.d/qt3-devel.csh /etc/profile.d/qt3-devel.sh this files are automatically sourced when tcsh or sh are started, and guess what? They define QTDIR to /usr/lib/qt3. You need not uninstalling those packages, simply move out of the way those two files by renaming them as /etc/profile.d/qt3-devel.csh.no /etc/profile.d/qt3-devel.sh.no Really it suffices that the extension be different from .csh or .sh. Time to update the wiki page, I guess... I am not sure anymore what is default and what I chose. Seems to me that I also installed some developer tools like bison and flex. So I will uninstall these three Qt3s and see what happens. Nope, didn't work. You have to run make confclean and configure again as you have /usr/lib/qt3 hardcoded in the Makefiles... Also, make sure that you do not have those files above in /etc/profile.d There was no /usr/lib/qt3 before I recently created it to accomodate the script error report. I found it here: Please, don't do that, fix the QTDIR problem, instead. $ sh link_includes link_includes: line 6: cd: /usr/lib/qt3/include: No such file or directory link_includes: line 20: cd: private: No such file or directory ln: creating symbolic link `./q*_p.h' to `../../src/*/q*_p.h': No such file or directory That is clearly an evidence that QTDIR is still set to /usr/lib/qt3 But the current link_includes, cd $QTDIR/include Maybe my environment is screwed up, I'll try printenv(print environment). QTDIR=/usr/lib/qt3 QMAKESPEC=/usr/lib/qt3/mkspecs/cygwin-g++ As I said above... I changed that to (because that was the configure switch) QMAKESPEC=/usr/local/src/qt3/mkspecs/cygwin-g++-win32 and QTDIR=/usr/local/src/qt3 I used tcsh for setenv QTDIR /usr/local/src/qt3 ? I better check the tcsh Path entry, none, I just added that with bash. The make completed with a few warnings. You can safely ignore them. --- 2. libdir='/usr/local/qt3/src/lib' to libdir='/usr/local/qt-cygwin/lib' Does line 2. have a transposition? should be .../src/qt3 Ops, you are right. I'll correct that. # Directory that this library needs to be installed in: libdir='/cygdrive/c/cygwin/usr/local/src/qt3/lib' I found the above ^^^ and changed it to below, keeping the full path. # Directory that this library needs to be installed in: libdir='/cygdrive/c/cygwin/usr/local/qt-cygwin/lib' I see that you use /cygdrive/c to access drive C:. If you issue the following command (you need to do it only once as the results are stored in a mount table): mount -f C: /c then you can write /c/path instead of /cygdrive/c/path to access the windows C:\path. Also, you don't need to write /cygdrive/c/cygwin/usr/local/qt-cygwin/lib but simply /usr/local/qt-cygwin/lib because when a path starts with / it refers to the cygwin root which is at /cygdrive/c/cygwin, in your case. -- Finished Qt3 and moving on to LyX hurrah! 3. Apply the following patch (fixes path_prefix handling): SH: Are the changes supposed to be applied as a manual edit? Yes, it is a so simple patch after all. Simply add the lines marked with a starting + . As you see in the patch, you should look around line 95 in the file src/support/environment.C. Looking forward for a working LyX/Cygwin ;-) -- Enrico
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: lyx-users@lists.lyx.org Sent: Friday, February 24, 2006 1:15 AM Subject: Re: LyX on Cygwin Stephen Harris [EMAIL PROTECTED] writes: You need not uninstalling those packages, simply move out of the way those two files by renaming them as /etc/profile.d/qt3-devel.csh.no /etc/profile.d/qt3-devel.sh.no I can reinstall them and rename them. I was toying with the idea of building a kde-cygwin desktop, maybe that is why I got them. I am not sure anymore what is default and what I chose. Seems to me that I also installed some developer tools like bison and flex. So I will uninstall these three Qt3s and see what happens. Nope, didn't work. You have to run make confclean and configure again as you have /usr/lib/qt3 hardcoded in the Makefiles... Also, make sure that you do not have those files above in /etc/profile.d I did run make confclean and also -R for the patch. But I used bash to set the environment. There was no /usr/lib/qt3 before I recently created it to accomodate the script error report. I found it here: Please, don't do that, fix the QTDIR problem, instead. Yes, I will clean that extra /lib directory up. Maybe my environment is screwed up, I'll try printenv(print environment). QTDIR=/usr/lib/qt3 QMAKESPEC=/usr/lib/qt3/mkspecs/cygwin-g++ As I said above... Yes. --- # Directory that this library needs to be installed in: libdir='/cygdrive/c/cygwin/usr/local/src/qt3/lib' I found the above ^^^ and changed it to below, keeping the full path. # Directory that this library needs to be installed in: libdir='/cygdrive/c/cygwin/usr/local/qt-cygwin/lib' I see that you use /cygdrive/c to access drive C:. If you issue the following command (you need to do it only once as the results are stored in a mount table): mount -f C: /c then you can write /c/path instead of /cygdrive/c/path to access the windows C:\path. Also, you don't need to write /cygdrive/c/cygwin/usr/local/qt-cygwin/lib but simply /usr/local/qt-cygwin/lib because when a path starts with / it refers to the cygwin root which is at /cygdrive/c/cygwin, in your case. Good, I will change that. Also I will look into that rsvt display. -- Finished Qt3 and moving on to LyX hurrah! 3. Apply the following patch (fixes path_prefix handling): SH: Are the changes supposed to be applied as a manual edit? Yes, it is a so simple patch after all. Simply add the lines marked with a starting + . As you see in the patch, you should look around line 95 in the file src/support/environment.C. Yes, it was fairly easy with your hint. I put the epstopdf and convert scripts in their own directoy at the beginning of PATH. Shouldn't I do something else to connect them to epstopdf.exe in Miktex\texmf and C:\ImageMagick\convert.exe ? I don't have Tetex installed and I think not Cygwin's ImageMagick. It seems too easy! Looking forward for a working LyX/Cygwin ;-) -- Enrico Thanks for all your help and tremendous effort in figuring out a working installation. I think it is miraculous that you could figure out all those configure switches. Now when somebody asks about Cygwin and LyX they can be pointed to your Wiki page. I'm writing this as I wait for make to finish. Thar she blows! I had to copy lyx(-qt).exe to c:\cygwin\bin because it complained about missing cywin1.dll and cygz.dll Regards, Stephen
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: lyx-users@lists.lyx.org Sent: Friday, February 24, 2006 6:29 AM Subject: Re: LyX on Cygwin On Fri, 24 Feb 2006 03:55:43 -0800, Stephen Harris wrote: Yes, it was fairly easy with your hint. I put the epstopdf and convert scripts in their own directoy at the beginning of PATH. Shouldn't I do something else to connect them to epstopdf.exe in Miktex\texmf and C:\ImageMagick\convert.exe ? I don't have Tetex installed and I think not Cygwin's ImageMagick. It seems too easy! You should do nothing apart assuring that they are in the system PATH which you can set through the Advanced tab in Control Panel-System or use path_prefix (see below). SH: I put C:\cygwin\bin in the PATH Thar she blows! I had to copy lyx(-qt).exe to c:\cygwin\bin because it complained about missing cywin1.dll and cygz.dll No, don't do that. Simply add C:\cygwin\bin to the PATH as explained above. You could set path_prefix as in the native version through LyX preferences. The path_prefix should be written in posix (cygwin) syntax and I suggest that you put as the first elements the following ones: /usr/local/bin:/usr/bin:/usr/X11R6/bin and then fill in whatever you like using ':' as a separator. In this way you can put the epstopdf and convert scripts in /usr/local/bin which is searched first. Once you filled in path_prefix in LyX as I suggested above, I think that you could also remove C:\cygwin\bin from the system PATH, but I have not checked it (Hmm... may be it doesn't work...) -- Enrico The View function doesn't work. It complains about missing TeX class article when I first load the .lyx document and C:\texmf~ is in my PATH. The Tex Information produces a window but it contains no information. I used mount -f C: /c (not mount -f C: /cygdrive/c ?) as advised. Path prefix had no entries which I thought was a bit strange. I've tried both of these in Path prefix C:/reader7/Reader/acrord32 /c/reader7/Reader/acrord32 I've tried both of these absolute paths in File formats Viewer C:/reader7/Reader/acrord32 /c/reader7/Reader/acrord32 originally it just said Viewer pdflatex, acrord32, but didn't work. The Working directory automatically generated by LyX is C:/Cygwin/.xemacs The tmp directory generated by LyX is C:/Cygwin/tmp I also tried putting C:/texmf/miktex/bin in Path prefix and also the path to article.cls which is in ~/.../base separated from each other with a : also :C:/reader7/etc I'm not sure what is broken because of being a Pre version. For instance Import Latex is missing, it just has text imports. The spellchecker starts checking the second misspelled word. Anyway your instructions are proven to work. A new user can search the archives and find clarifications in this thread. I've remembered to modify, apply, save, and Reconfigure. My favorite test file, sample.lyx, does convert eps and jpeg, Stephen
Re: LyX on Cygwin
On Fri, 24 Feb 2006 14:13:04 -0800, Stephen Harris wrote: The View function doesn't work. It complains about missing TeX class article when I first load the .lyx document and C:\texmf~ is in my PATH. Try reconfiguring after adjusting path_prefix (see below). The Tex Information produces a window but it contains no information. Yes, I also see this, but then this also happens with 1.3.7. I used mount -f C: /c (not mount -f C: /cygdrive/c ?) as advised. Correct. To see if that works try ls /c in a cygwin shell. Path prefix had no entries which I thought was a bit strange. It is normal. In 1.3.7 entries are added by the windows installer. I've tried both of these in Path prefix C:/reader7/Reader/acrord32 /c/reader7/Reader/acrord32 I've tried both of these absolute paths in File formats Viewer C:/reader7/Reader/acrord32 /c/reader7/Reader/acrord32 originally it just said Viewer pdflatex, acrord32, but didn't work. Please *always* use posix syntax in path_prefix, i.e., /c/reader7/... and *not* C:/reader7/... The Working directory automatically generated by LyX is C:/Cygwin/.xemacs Uh? It seems that you have not set the HOME variable. LyX/Cygwin uses HOME instead of USERPROFILE. Perhaps I should patch the sources such that USERPROFILE is used as a fallback if HOME is not set. For the moment, you can fix this by adding the HOME var in the same way you add the PATH var but in the user section. Set HOME to a folder of your choice and then try launching LyX with the option -dbg init to see what it thinks your home_dir is. The tmp directory generated by LyX is C:/Cygwin/tmp This is correct. I also tried putting C:/texmf/miktex/bin in Path prefix and also the path to article.cls which is in ~/.../base separated from each other with a : also :C:/reader7/etc As I noted above, always use posix syntax in path_prefix, so write that as /c/texmf/miktex/bin:/c/reader7/etc The ':' char must only be used as a separator. Please try the following as path_prefix (I am assuming that your AcroRd32.exe is in C:\reader7\Reader\acrord32 and that you issued the mount -f C: /c command) /usr/local/bin:/usr/bin:/usr/X11R6/bin:/c/texmf/miktex/bin:/c/reader7/Reader/acrord32 After modifying path_prefix, save the preferences and *restart* LyX. I'm not sure what is broken because of being a Pre version. For instance Import Latex is missing, it just has text imports. This is a known issue when a version suffix is used (the configure script should be called with the option --version-suffix=the_suffix but it is not). To fix this do the following in a cygwin shell: cd /usr/local/bin ln -s tex2lyx-1.4.0.exe tex2lyx and then reconfigure LyX. The spellchecker starts checking the second misspelled word. This also is a known bug in LyX. Anyway your instructions are proven to work. A new user can search the archives and find clarifications in this thread. I've remembered to modify, apply, save, and Reconfigure. My favorite test file, sample.lyx, does convert eps and jpeg, I think that you have a working copy of LyX. You should simply fix some glitches. -- Enrico
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: lyx-users@lists.lyx.org Sent: Friday, February 24, 2006 4:33 PM Subject: Re: LyX on Cygwin On Fri, 24 Feb 2006 14:13:04 -0800, Stephen Harris wrote: The View function doesn't work. It complains about missing TeX class article when I first load the .lyx document and C:\texmf~ is in my PATH. Try reconfiguring after adjusting path_prefix (see below). SH: The rest of the error message is LyX will not be able to produce output. The Tex Information produces a window but it contains no information. Yes, I also see this, but then this also happens with 1.3.7. Perhaps normal for Cygwin/Linux but you can see all these files and their paths with Uwe or Angus native LyXwin. Or with Mingw build of LyX1.4.0_pre3. It is how I used to check that LyX communicated with Miktex:texmf I used mount -f C: /c (not mount -f C: /cygdrive/c ?) as advised. Correct. To see if that works try ls /c in a cygwin shell. Yes I see lots of my stuff. When I use File-Open it still displays the path in terms of /cygdrive/c/ which makes me nervous. Path prefix had no entries which I thought was a bit strange. It is normal. In 1.3.7 entries are added by the windows installer. I've tried both of these in Path prefix C:/reader7/Reader/acrord32 /c/reader7/Reader/acrord32 I've tried both of these absolute paths in File formats Viewer C:/reader7/Reader/acrord32 /c/reader7/Reader/acrord32 originally it just said Viewer pdflatex, acrord32, but didn't work. Please *always* use posix syntax in path_prefix, i.e., /c/reader7/... and *not* C:/reader7/... Ok, the reason I tried both was because /c/reader7/Reader/acrord32 failed to enable the pdflatex Viewing function. The Working directory automatically generated by LyX is C:/Cygwin/.xemacs Uh? It seems that you have not set the HOME variable. LyX/Cygwin uses HOME instead of USERPROFILE. Perhaps I should patch the sources such that USERPROFILE is used as a fallback if HOME is not set. For the moment, you can fix this by adding the HOME var in the same way you add the PATH var but in the user section. Set HOME to a folder of your choice and then try launching LyX with the option -dbg init to see what it thinks your home_dir is. I used to have Xemacs for Cygwin installed. I set the HOME variable to C:\Cygwin\.xemacs for it. I now have another version of Xemacs set to HOME there also so if I change it I have to move init.el files etc. The tmp directory generated by LyX is C:/Cygwin/tmp This is correct. I also tried putting C:/texmf/miktex/bin in Path prefix and also the path to article.cls which is in ~/.../base separated from each other with a : also :C:/reader7/etc As I noted above, always use posix syntax in path_prefix, so write that as /c/texmf/miktex/bin:/c/reader7/etc The ':' char must only be used as a separator. Please try the following as path_prefix (I am assuming that your AcroRd32.exe is in C:\reader7\Reader\acrord32 and that you issued the mount -f C: /c command) /usr/local/bin:/usr/bin:/usr/X11R6/bin:/c/texmf/miktex/bin:/c/reader7/Reader/acrord32 Oops. No acrord32 is short for the acrord32.exe I just noticed this after trying it and it failed. So I tried :/c/reader7/Reader/ which didn't work. I just tried it without the trailing slash /, and it didn't work. I start LyX with an icon linked to C:\cygwin\usr\local\bin\LyX-1.4.0.exe and it gives me an error message Locale en_US could not be set which has never mattered in the past. My language is set to English in LyX. The Locale error follows after the LyX will not be able to produce output. After modifying path_prefix, save the preferences and *restart* LyX. I did that. I did that, tried Reconfigure, closed and opened, to no avail. I'm not sure what is broken because of being a Pre version. For instance Import Latex is missing, it just has text imports. This is a known issue when a version suffix is used (the configure script should be called with the option --version-suffix=the_suffix but it is not). To fix this do the following in a cygwin shell: cd /usr/local/bin ln -s tex2lyx-1.4.0.exe tex2lyx and then reconfigure LyX. By cracky it worked! I can now import Latex. Anyway your instructions are proven to work. A new user can search the archives and find clarifications in this thread. I've remembered to modify, apply, save, and Reconfigure. My favorite test file, sample.lyx, does convert eps and jpeg, I think that you have a working copy of LyX. You should simply fix some glitches. -- Enrico I've watched Reconfigure process. It says yes to finding pdflatex and acrord32 and gsview32. I don't have any Viewers, no DVI or Postscript. I added :/c/gs/gs8.51/bin:/c/ghostgum/gsview to Path prefix and turned on Instant Preview. No previewers. Before when I had this problem I ran sh configure from lyx/resources/lyx I'll give that -dbg init a try
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: lyx-users@lists.lyx.org Sent: Thursday, February 23, 2006 7:52 PM Subject: Re: LyX on Cygwin Stephen Harris [EMAIL PROTECTED] writes: Uh, oh... have you installed the cygwin Qt package by chance? But I do have a .../mkspecs/cygwin-g++-win32/i386pe.x.-no-rdat C:\Cygwin\usr\local\src\qt3\mkspecs That file etc. didn't get copied over to the /lib directory by the script. So I made this .../i386pe.x.-no-rdat conform to the script, but no dice. Copied what I found to where the script said it looked and couldn't find. Well, you should need to do no more and no less than what I put on the wiki, otherwise it means that somenthing is going wrong... Next I notice C:\Cygwin\usr\lib\gcc\i686-pc-cygwin\3.4.4\include\c++\i686-pc-cygwin has no /bin and no ld. It just contains a directory called /bits So I made that conform to the script (mkdir bin and copied /bin files). Run /usr/bin/make confclean; set the Path and Qtdir again; run link_includes; run configure again with all options; edit all: # line; then /usr/bin/make; Returned same error: /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot open linker script file /usr/lib/qt3/mkspecs/cygwin-g++-win32/i386pe.x-no-rdata: No such file or directory collect2: ld returned 1 exit status make[2]: *** [../../bin/moc] Error 1 make[2]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3/src/moc' make[1]: *** [src-moc] Error 2 make[1]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3' I cannot understand from where that prefix /usr/lib/qt3 comes from. If you have installed the official cygwin Qt packages, perhaps this is a symptom of a sort of clashing. -- Enrico [EMAIL PROTECTED] /cygdrive/c/cygwin/usr/local/src/qt3 $ ./configure -platform cygwin-g++-win32 -v -release -static -qt-imgfmt-png etc. So no it is not dynamic, I use this copy and paste every time which is free of typos. But, I do have Qt3-C++/-bin/-devel all installed. I am not sure anymore what is default and what I chose. Seems to me that I also installed some developer tools like bison and flex. So I will uninstall these three Qt3s and see what happens. Nope, didn't work. There was no /usr/lib/qt3 before I recently created it to accomodate the script error report. I found it here: $ sh link_includes link_includes: line 6: cd: /usr/lib/qt3/include: No such file or directory link_includes: line 20: cd: private: No such file or directory ln: creating symbolic link `./q*_p.h' to `../../src/*/q*_p.h': No such file or directory But the current link_includes, cd $QTDIR/include Maybe my environment is screwed up, I'll try printenv(print environment). QTDIR=/usr/lib/qt3 QMAKESPEC=/usr/lib/qt3/mkspecs/cygwin-g++ I changed that to (because that was the configure switch) QMAKESPEC=/usr/local/src/qt3/mkspecs/cygwin-g++-win32 and QTDIR=/usr/local/src/qt3 I used tcsh for setenv QTDIR /usr/local/src/qt3 ? I better check the tcsh Path entry, none, I just added that with bash. The make completed with a few warnings. --- 2. libdir='/usr/local/qt3/src/lib' to libdir='/usr/local/qt-cygwin/lib' Does line 2. have a transposition? should be .../src/qt3 # Directory that this library needs to be installed in: libdir='/cygdrive/c/cygwin/usr/local/src/qt3/lib' I found the above ^^^ and changed it to below, keeping the full path. # Directory that this library needs to be installed in: libdir='/cygdrive/c/cygwin/usr/local/qt-cygwin/lib' -- Finished Qt3 and moving on to LyX 3. Apply the following patch (fixes path_prefix handling): SH: Are the changes supposed to be applied as a manual edit? Regards, Stephen
Re: LyX on Cygwin
Stephen Harris [EMAIL PROTECTED] writes: Stephen at textonyx /cygdrive/c/cygwin/usr/local/src/qt3 $ ./configure -platform cygwin-g++-win32 -v -release -static -qt-imgfmt-png etc. So no it is not dynamic, I use this copy and paste every time which is free of typos. But, I do have Qt3-C++/-bin/-devel all installed. So that's the problem. I investigated a bit and found that qt3-devel is the culprit. It installs the following two files: /etc/profile.d/qt3-devel.csh /etc/profile.d/qt3-devel.sh this files are automatically sourced when tcsh or sh are started, and guess what? They define QTDIR to /usr/lib/qt3. You need not uninstalling those packages, simply move out of the way those two files by renaming them as /etc/profile.d/qt3-devel.csh.no /etc/profile.d/qt3-devel.sh.no Really it suffices that the extension be different from .csh or .sh. Time to update the wiki page, I guess... I am not sure anymore what is default and what I chose. Seems to me that I also installed some developer tools like bison and flex. So I will uninstall these three Qt3s and see what happens. Nope, didn't work. You have to run make confclean and configure again as you have /usr/lib/qt3 hardcoded in the Makefiles... Also, make sure that you do not have those files above in /etc/profile.d There was no /usr/lib/qt3 before I recently created it to accomodate the script error report. I found it here: Please, don't do that, fix the QTDIR problem, instead. $ sh link_includes link_includes: line 6: cd: /usr/lib/qt3/include: No such file or directory link_includes: line 20: cd: private: No such file or directory ln: creating symbolic link `./q*_p.h' to `../../src/*/q*_p.h': No such file or directory That is clearly an evidence that QTDIR is still set to /usr/lib/qt3 But the current link_includes, cd $QTDIR/include Maybe my environment is screwed up, I'll try printenv(print environment). QTDIR=/usr/lib/qt3 QMAKESPEC=/usr/lib/qt3/mkspecs/cygwin-g++ As I said above... I changed that to (because that was the configure switch) QMAKESPEC=/usr/local/src/qt3/mkspecs/cygwin-g++-win32 and QTDIR=/usr/local/src/qt3 I used tcsh for setenv QTDIR /usr/local/src/qt3 ? I better check the tcsh Path entry, none, I just added that with bash. The make completed with a few warnings. You can safely ignore them. --- 2. libdir='/usr/local/qt3/src/lib' to libdir='/usr/local/qt-cygwin/lib' Does line 2. have a transposition? should be .../src/qt3 Ops, you are right. I'll correct that. # Directory that this library needs to be installed in: libdir='/cygdrive/c/cygwin/usr/local/src/qt3/lib' I found the above ^^^ and changed it to below, keeping the full path. # Directory that this library needs to be installed in: libdir='/cygdrive/c/cygwin/usr/local/qt-cygwin/lib' I see that you use /cygdrive/c to access drive C:. If you issue the following command (you need to do it only once as the results are stored in a mount table): mount -f C: /c then you can write /c/path instead of /cygdrive/c/path to access the windows C:\path. Also, you don't need to write /cygdrive/c/cygwin/usr/local/qt-cygwin/lib but simply /usr/local/qt-cygwin/lib because when a path starts with / it refers to the cygwin root which is at /cygdrive/c/cygwin, in your case. -- Finished Qt3 and moving on to LyX hurrah! 3. Apply the following patch (fixes path_prefix handling): SH: Are the changes supposed to be applied as a manual edit? Yes, it is a so simple patch after all. Simply add the lines marked with a starting + . As you see in the patch, you should look around line 95 in the file src/support/environment.C. Looking forward for a working LyX/Cygwin ;-) -- Enrico
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: lyx-users@lists.lyx.org Sent: Friday, February 24, 2006 1:15 AM Subject: Re: LyX on Cygwin Stephen Harris [EMAIL PROTECTED] writes: You need not uninstalling those packages, simply move out of the way those two files by renaming them as /etc/profile.d/qt3-devel.csh.no /etc/profile.d/qt3-devel.sh.no I can reinstall them and rename them. I was toying with the idea of building a kde-cygwin desktop, maybe that is why I got them. I am not sure anymore what is default and what I chose. Seems to me that I also installed some developer tools like bison and flex. So I will uninstall these three Qt3s and see what happens. Nope, didn't work. You have to run make confclean and configure again as you have /usr/lib/qt3 hardcoded in the Makefiles... Also, make sure that you do not have those files above in /etc/profile.d I did run make confclean and also -R for the patch. But I used bash to set the environment. There was no /usr/lib/qt3 before I recently created it to accomodate the script error report. I found it here: Please, don't do that, fix the QTDIR problem, instead. Yes, I will clean that extra /lib directory up. Maybe my environment is screwed up, I'll try printenv(print environment). QTDIR=/usr/lib/qt3 QMAKESPEC=/usr/lib/qt3/mkspecs/cygwin-g++ As I said above... Yes. --- # Directory that this library needs to be installed in: libdir='/cygdrive/c/cygwin/usr/local/src/qt3/lib' I found the above ^^^ and changed it to below, keeping the full path. # Directory that this library needs to be installed in: libdir='/cygdrive/c/cygwin/usr/local/qt-cygwin/lib' I see that you use /cygdrive/c to access drive C:. If you issue the following command (you need to do it only once as the results are stored in a mount table): mount -f C: /c then you can write /c/path instead of /cygdrive/c/path to access the windows C:\path. Also, you don't need to write /cygdrive/c/cygwin/usr/local/qt-cygwin/lib but simply /usr/local/qt-cygwin/lib because when a path starts with / it refers to the cygwin root which is at /cygdrive/c/cygwin, in your case. Good, I will change that. Also I will look into that rsvt display. -- Finished Qt3 and moving on to LyX hurrah! 3. Apply the following patch (fixes path_prefix handling): SH: Are the changes supposed to be applied as a manual edit? Yes, it is a so simple patch after all. Simply add the lines marked with a starting + . As you see in the patch, you should look around line 95 in the file src/support/environment.C. Yes, it was fairly easy with your hint. I put the epstopdf and convert scripts in their own directoy at the beginning of PATH. Shouldn't I do something else to connect them to epstopdf.exe in Miktex\texmf and C:\ImageMagick\convert.exe ? I don't have Tetex installed and I think not Cygwin's ImageMagick. It seems too easy! Looking forward for a working LyX/Cygwin ;-) -- Enrico Thanks for all your help and tremendous effort in figuring out a working installation. I think it is miraculous that you could figure out all those configure switches. Now when somebody asks about Cygwin and LyX they can be pointed to your Wiki page. I'm writing this as I wait for make to finish. Thar she blows! I had to copy lyx(-qt).exe to c:\cygwin\bin because it complained about missing cywin1.dll and cygz.dll Regards, Stephen
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: lyx-users@lists.lyx.org Sent: Friday, February 24, 2006 6:29 AM Subject: Re: LyX on Cygwin On Fri, 24 Feb 2006 03:55:43 -0800, Stephen Harris wrote: Yes, it was fairly easy with your hint. I put the epstopdf and convert scripts in their own directoy at the beginning of PATH. Shouldn't I do something else to connect them to epstopdf.exe in Miktex\texmf and C:\ImageMagick\convert.exe ? I don't have Tetex installed and I think not Cygwin's ImageMagick. It seems too easy! You should do nothing apart assuring that they are in the system PATH which you can set through the Advanced tab in Control Panel-System or use path_prefix (see below). SH: I put C:\cygwin\bin in the PATH Thar she blows! I had to copy lyx(-qt).exe to c:\cygwin\bin because it complained about missing cywin1.dll and cygz.dll No, don't do that. Simply add C:\cygwin\bin to the PATH as explained above. You could set path_prefix as in the native version through LyX preferences. The path_prefix should be written in posix (cygwin) syntax and I suggest that you put as the first elements the following ones: /usr/local/bin:/usr/bin:/usr/X11R6/bin and then fill in whatever you like using ':' as a separator. In this way you can put the epstopdf and convert scripts in /usr/local/bin which is searched first. Once you filled in path_prefix in LyX as I suggested above, I think that you could also remove C:\cygwin\bin from the system PATH, but I have not checked it (Hmm... may be it doesn't work...) -- Enrico The View function doesn't work. It complains about missing TeX class article when I first load the .lyx document and C:\texmf~ is in my PATH. The Tex Information produces a window but it contains no information. I used mount -f C: /c (not mount -f C: /cygdrive/c ?) as advised. Path prefix had no entries which I thought was a bit strange. I've tried both of these in Path prefix C:/reader7/Reader/acrord32 /c/reader7/Reader/acrord32 I've tried both of these absolute paths in File formats Viewer C:/reader7/Reader/acrord32 /c/reader7/Reader/acrord32 originally it just said Viewer pdflatex, acrord32, but didn't work. The Working directory automatically generated by LyX is C:/Cygwin/.xemacs The tmp directory generated by LyX is C:/Cygwin/tmp I also tried putting C:/texmf/miktex/bin in Path prefix and also the path to article.cls which is in ~/.../base separated from each other with a : also :C:/reader7/etc I'm not sure what is broken because of being a Pre version. For instance Import Latex is missing, it just has text imports. The spellchecker starts checking the second misspelled word. Anyway your instructions are proven to work. A new user can search the archives and find clarifications in this thread. I've remembered to modify, apply, save, and Reconfigure. My favorite test file, sample.lyx, does convert eps and jpeg, Stephen
Re: LyX on Cygwin
On Fri, 24 Feb 2006 14:13:04 -0800, Stephen Harris wrote: The View function doesn't work. It complains about missing TeX class article when I first load the .lyx document and C:\texmf~ is in my PATH. Try reconfiguring after adjusting path_prefix (see below). The Tex Information produces a window but it contains no information. Yes, I also see this, but then this also happens with 1.3.7. I used mount -f C: /c (not mount -f C: /cygdrive/c ?) as advised. Correct. To see if that works try ls /c in a cygwin shell. Path prefix had no entries which I thought was a bit strange. It is normal. In 1.3.7 entries are added by the windows installer. I've tried both of these in Path prefix C:/reader7/Reader/acrord32 /c/reader7/Reader/acrord32 I've tried both of these absolute paths in File formats Viewer C:/reader7/Reader/acrord32 /c/reader7/Reader/acrord32 originally it just said Viewer pdflatex, acrord32, but didn't work. Please *always* use posix syntax in path_prefix, i.e., /c/reader7/... and *not* C:/reader7/... The Working directory automatically generated by LyX is C:/Cygwin/.xemacs Uh? It seems that you have not set the HOME variable. LyX/Cygwin uses HOME instead of USERPROFILE. Perhaps I should patch the sources such that USERPROFILE is used as a fallback if HOME is not set. For the moment, you can fix this by adding the HOME var in the same way you add the PATH var but in the user section. Set HOME to a folder of your choice and then try launching LyX with the option -dbg init to see what it thinks your home_dir is. The tmp directory generated by LyX is C:/Cygwin/tmp This is correct. I also tried putting C:/texmf/miktex/bin in Path prefix and also the path to article.cls which is in ~/.../base separated from each other with a : also :C:/reader7/etc As I noted above, always use posix syntax in path_prefix, so write that as /c/texmf/miktex/bin:/c/reader7/etc The ':' char must only be used as a separator. Please try the following as path_prefix (I am assuming that your AcroRd32.exe is in C:\reader7\Reader\acrord32 and that you issued the mount -f C: /c command) /usr/local/bin:/usr/bin:/usr/X11R6/bin:/c/texmf/miktex/bin:/c/reader7/Reader/acrord32 After modifying path_prefix, save the preferences and *restart* LyX. I'm not sure what is broken because of being a Pre version. For instance Import Latex is missing, it just has text imports. This is a known issue when a version suffix is used (the configure script should be called with the option --version-suffix=the_suffix but it is not). To fix this do the following in a cygwin shell: cd /usr/local/bin ln -s tex2lyx-1.4.0.exe tex2lyx and then reconfigure LyX. The spellchecker starts checking the second misspelled word. This also is a known bug in LyX. Anyway your instructions are proven to work. A new user can search the archives and find clarifications in this thread. I've remembered to modify, apply, save, and Reconfigure. My favorite test file, sample.lyx, does convert eps and jpeg, I think that you have a working copy of LyX. You should simply fix some glitches. -- Enrico
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: lyx-users@lists.lyx.org Sent: Friday, February 24, 2006 4:33 PM Subject: Re: LyX on Cygwin On Fri, 24 Feb 2006 14:13:04 -0800, Stephen Harris wrote: The View function doesn't work. It complains about missing TeX class article when I first load the .lyx document and C:\texmf~ is in my PATH. Try reconfiguring after adjusting path_prefix (see below). SH: The rest of the error message is LyX will not be able to produce output. The Tex Information produces a window but it contains no information. Yes, I also see this, but then this also happens with 1.3.7. Perhaps normal for Cygwin/Linux but you can see all these files and their paths with Uwe or Angus native LyXwin. Or with Mingw build of LyX1.4.0_pre3. It is how I used to check that LyX communicated with Miktex:texmf I used mount -f C: /c (not mount -f C: /cygdrive/c ?) as advised. Correct. To see if that works try ls /c in a cygwin shell. Yes I see lots of my stuff. When I use File-Open it still displays the path in terms of /cygdrive/c/ which makes me nervous. Path prefix had no entries which I thought was a bit strange. It is normal. In 1.3.7 entries are added by the windows installer. I've tried both of these in Path prefix C:/reader7/Reader/acrord32 /c/reader7/Reader/acrord32 I've tried both of these absolute paths in File formats Viewer C:/reader7/Reader/acrord32 /c/reader7/Reader/acrord32 originally it just said Viewer pdflatex, acrord32, but didn't work. Please *always* use posix syntax in path_prefix, i.e., /c/reader7/... and *not* C:/reader7/... Ok, the reason I tried both was because /c/reader7/Reader/acrord32 failed to enable the pdflatex Viewing function. The Working directory automatically generated by LyX is C:/Cygwin/.xemacs Uh? It seems that you have not set the HOME variable. LyX/Cygwin uses HOME instead of USERPROFILE. Perhaps I should patch the sources such that USERPROFILE is used as a fallback if HOME is not set. For the moment, you can fix this by adding the HOME var in the same way you add the PATH var but in the user section. Set HOME to a folder of your choice and then try launching LyX with the option -dbg init to see what it thinks your home_dir is. I used to have Xemacs for Cygwin installed. I set the HOME variable to C:\Cygwin\.xemacs for it. I now have another version of Xemacs set to HOME there also so if I change it I have to move init.el files etc. The tmp directory generated by LyX is C:/Cygwin/tmp This is correct. I also tried putting C:/texmf/miktex/bin in Path prefix and also the path to article.cls which is in ~/.../base separated from each other with a : also :C:/reader7/etc As I noted above, always use posix syntax in path_prefix, so write that as /c/texmf/miktex/bin:/c/reader7/etc The ':' char must only be used as a separator. Please try the following as path_prefix (I am assuming that your AcroRd32.exe is in C:\reader7\Reader\acrord32 and that you issued the mount -f C: /c command) /usr/local/bin:/usr/bin:/usr/X11R6/bin:/c/texmf/miktex/bin:/c/reader7/Reader/acrord32 Oops. No acrord32 is short for the acrord32.exe I just noticed this after trying it and it failed. So I tried :/c/reader7/Reader/ which didn't work. I just tried it without the trailing slash /, and it didn't work. I start LyX with an icon linked to C:\cygwin\usr\local\bin\LyX-1.4.0.exe and it gives me an error message Locale en_US could not be set which has never mattered in the past. My language is set to English in LyX. The Locale error follows after the LyX will not be able to produce output. After modifying path_prefix, save the preferences and *restart* LyX. I did that. I did that, tried Reconfigure, closed and opened, to no avail. I'm not sure what is broken because of being a Pre version. For instance Import Latex is missing, it just has text imports. This is a known issue when a version suffix is used (the configure script should be called with the option --version-suffix=the_suffix but it is not). To fix this do the following in a cygwin shell: cd /usr/local/bin ln -s tex2lyx-1.4.0.exe tex2lyx and then reconfigure LyX. By cracky it worked! I can now import Latex. Anyway your instructions are proven to work. A new user can search the archives and find clarifications in this thread. I've remembered to modify, apply, save, and Reconfigure. My favorite test file, sample.lyx, does convert eps and jpeg, I think that you have a working copy of LyX. You should simply fix some glitches. -- Enrico I've watched Reconfigure process. It says yes to finding pdflatex and acrord32 and gsview32. I don't have any Viewers, no DVI or Postscript. I added :/c/gs/gs8.51/bin:/c/ghostgum/gsview to Path prefix and turned on Instant Preview. No previewers. Before when I had this problem I ran sh configure from lyx/resources/lyx I'll give that -dbg init a try
Re: LyX on Cygwin
- Original Message - From: "Enrico Forestieri" <[EMAIL PROTECTED]> To: <lyx-users@lists.lyx.org> Sent: Thursday, February 23, 2006 7:52 PM Subject: Re: LyX on Cygwin Stephen Harris <[EMAIL PROTECTED]> writes: Uh, oh... have you installed the cygwin Qt package by chance? But I do have a .../mkspecs/cygwin-g++-win32/i386pe.x.-no-rdat C:\Cygwin\usr\local\src\qt3\mkspecs That file etc. didn't get copied over to the /lib directory by the script. So I made this .../i386pe.x.-no-rdat conform to the script, but no dice. Copied what I found to where the script said it looked and couldn't find. Well, you should need to do no more and no less than what I put on the wiki, otherwise it means that somenthing is going wrong... Next I notice C:\Cygwin\usr\lib\gcc\i686-pc-cygwin\3.4.4\include\c++\i686-pc-cygwin has no /bin and no ld. It just contains a directory called /bits So I made that conform to the script (mkdir bin and copied /bin files). Run /usr/bin/make confclean; set the Path and Qtdir again; run link_includes; run configure again with all options; edit all: # line; then /usr/bin/make; Returned same error: /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot open linker script file /usr/lib/qt3/mkspecs/cygwin-g++-win32/i386pe.x-no-rdata: No such file or directory collect2: ld returned 1 exit status make[2]: *** [../../bin/moc] Error 1 make[2]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3/src/moc' make[1]: *** [src-moc] Error 2 make[1]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3' I cannot understand from where that prefix "/usr/lib/qt3" comes from. If you have installed the official cygwin Qt packages, perhaps this is a symptom of a sort of clashing. -- Enrico [EMAIL PROTECTED] /cygdrive/c/cygwin/usr/local/src/qt3 $ ./configure -platform cygwin-g++-win32 -v -release -static -qt-imgfmt-png etc. So no it is not dynamic, I use this copy and paste every time which is free of typos. But, I do have Qt3-C++/-bin/-devel all installed. I am not sure anymore what is default and what I chose. Seems to me that I also installed some developer tools like bison and flex. So I will uninstall these three Qt3s and see what happens. Nope, didn't work. There was no /usr/lib/qt3 before I recently created it to accomodate the script error report. I found it here: $ sh link_includes link_includes: line 6: cd: /usr/lib/qt3/include: No such file or directory link_includes: line 20: cd: private: No such file or directory ln: creating symbolic link `./q*_p.h' to `../../src/*/q*_p.h': No such file or directory But the current link_includes, cd "$QTDIR/include" Maybe my environment is screwed up, I'll try printenv(print environment). QTDIR=/usr/lib/qt3 QMAKESPEC=/usr/lib/qt3/mkspecs/cygwin-g++ I changed that to (because that was the configure switch) QMAKESPEC=/usr/local/src/qt3/mkspecs/cygwin-g++-win32 and QTDIR=/usr/local/src/qt3 I used tcsh for setenv QTDIR /usr/local/src/qt3 ? I better check the tcsh Path entry, none, I just added that with bash. The make completed with a few warnings. --- 2. libdir='/usr/local/qt3/src/lib' to libdir='/usr/local/qt-cygwin/lib' Does line 2. have a transposition? should be .../src/qt3 # Directory that this library needs to be installed in: libdir='/cygdrive/c/cygwin/usr/local/src/qt3/lib' I found the above ^^^ and changed it to below, keeping the full path. # Directory that this library needs to be installed in: libdir='/cygdrive/c/cygwin/usr/local/qt-cygwin/lib' -- Finished Qt3 and moving on to LyX 3. "Apply the following patch (fixes path_prefix handling):" SH: Are the changes supposed to be applied as a manual edit? Regards, Stephen
Re: LyX on Cygwin
Stephen Harris <[EMAIL PROTECTED]> writes: > > Stephen textonyx /cygdrive/c/cygwin/usr/local/src/qt3 > $ ./configure -platform cygwin-g++-win32 -v -release -static -qt-imgfmt-png > etc. > > So no it is not dynamic, I use this copy and paste every time > which is free of typos. But, I do have Qt3-C++/-bin/-devel all installed. So that's the problem. I investigated a bit and found that qt3-devel is the culprit. It installs the following two files: /etc/profile.d/qt3-devel.csh /etc/profile.d/qt3-devel.sh this files are automatically sourced when tcsh or sh are started, and guess what? They define QTDIR to /usr/lib/qt3. You need not uninstalling those packages, simply move out of the way those two files by renaming them as /etc/profile.d/qt3-devel.csh.no /etc/profile.d/qt3-devel.sh.no Really it suffices that the extension be different from .csh or .sh. Time to update the wiki page, I guess... > I am not sure anymore what is default and what I chose. Seems to me > that I also installed some developer tools like bison and flex. So I will > uninstall these three Qt3s and see what happens. Nope, didn't work. You have to run "make confclean" and configure again as you have /usr/lib/qt3 hardcoded in the Makefiles... Also, make sure that you do not have those files above in /etc/profile.d > There was no /usr/lib/qt3 before I recently created it to accomodate > the script error report. I found it here: Please, don't do that, fix the QTDIR problem, instead. > $ sh link_includes > link_includes: line 6: cd: /usr/lib/qt3/include: No such file or directory > link_includes: line 20: cd: private: No such file or directory > ln: creating symbolic link `./q*_p.h' to `../../src/*/q*_p.h': No such file > or > directory That is clearly an evidence that QTDIR is still set to /usr/lib/qt3 > But the current link_includes, cd "$QTDIR/include" > > Maybe my environment is screwed up, I'll try printenv(print environment). > > QTDIR=/usr/lib/qt3 > QMAKESPEC=/usr/lib/qt3/mkspecs/cygwin-g++ As I said above... > I changed that to (because that was the configure switch) > QMAKESPEC=/usr/local/src/qt3/mkspecs/cygwin-g++-win32 > and QTDIR=/usr/local/src/qt3 > I used tcsh for setenv QTDIR /usr/local/src/qt3 ? > I better check the tcsh Path entry, none, I just added that with bash. > > The make completed with a few warnings. You can safely ignore them. > --- > > 2. libdir='/usr/local/qt3/src/lib' > to libdir='/usr/local/qt-cygwin/lib' > > Does line 2. have a transposition? should be .../src/qt3 Ops, you are right. I'll correct that. > # Directory that this library needs to be installed in: > libdir='/cygdrive/c/cygwin/usr/local/src/qt3/lib' > > I found the above ^^^ and changed it to below, keeping the full path. > # Directory that this library needs to be installed in: > libdir='/cygdrive/c/cygwin/usr/local/qt-cygwin/lib' I see that you use /cygdrive/c to access drive C:. If you issue the following command (you need to do it only once as the results are stored in a mount table): mount -f C: /c then you can write /c/path instead of /cygdrive/c/path to access the windows C:\path. Also, you don't need to write "/cygdrive/c/cygwin/usr/local/qt-cygwin/lib" but simply "/usr/local/qt-cygwin/lib" because when a path starts with "/" it refers to the cygwin root which is at /cygdrive/c/cygwin, in your case. > -- > > Finished Qt3 and moving on to LyX hurrah! > 3. "Apply the following patch (fixes path_prefix handling):" > SH: Are the changes supposed to be applied as a manual edit? Yes, it is a so simple patch after all. Simply add the lines marked with a starting + . As you see in the patch, you should look around line 95 in the file src/support/environment.C. Looking forward for a working LyX/Cygwin ;-) -- Enrico
Re: LyX on Cygwin
- Original Message - From: "Enrico Forestieri" <[EMAIL PROTECTED]> To: <lyx-users@lists.lyx.org> Sent: Friday, February 24, 2006 1:15 AM Subject: Re: LyX on Cygwin Stephen Harris <[EMAIL PROTECTED]> writes: You need not uninstalling those packages, simply move out of the way those two files by renaming them as /etc/profile.d/qt3-devel.csh.no /etc/profile.d/qt3-devel.sh.no I can reinstall them and rename them. I was toying with the idea of building a kde-cygwin desktop, maybe that is why I got them. I am not sure anymore what is default and what I chose. Seems to me that I also installed some developer tools like bison and flex. So I will uninstall these three Qt3s and see what happens. Nope, didn't work. You have to run "make confclean" and configure again as you have /usr/lib/qt3 hardcoded in the Makefiles... Also, make sure that you do not have those files above in /etc/profile.d I did run make confclean and also -R for the patch. But I used bash to set the environment. There was no /usr/lib/qt3 before I recently created it to accomodate the script error report. I found it here: Please, don't do that, fix the QTDIR problem, instead. Yes, I will clean that extra /lib directory up. Maybe my environment is screwed up, I'll try printenv(print environment). QTDIR=/usr/lib/qt3 QMAKESPEC=/usr/lib/qt3/mkspecs/cygwin-g++ As I said above... Yes. --- # Directory that this library needs to be installed in: libdir='/cygdrive/c/cygwin/usr/local/src/qt3/lib' I found the above ^^^ and changed it to below, keeping the full path. # Directory that this library needs to be installed in: libdir='/cygdrive/c/cygwin/usr/local/qt-cygwin/lib' I see that you use /cygdrive/c to access drive C:. If you issue the following command (you need to do it only once as the results are stored in a mount table): mount -f C: /c then you can write /c/path instead of /cygdrive/c/path to access the windows C:\path. Also, you don't need to write "/cygdrive/c/cygwin/usr/local/qt-cygwin/lib" but simply "/usr/local/qt-cygwin/lib" because when a path starts with "/" it refers to the cygwin root which is at /cygdrive/c/cygwin, in your case. Good, I will change that. Also I will look into that rsvt display. -- Finished Qt3 and moving on to LyX hurrah! 3. "Apply the following patch (fixes path_prefix handling):" SH: Are the changes supposed to be applied as a manual edit? Yes, it is a so simple patch after all. Simply add the lines marked with a starting + . As you see in the patch, you should look around line 95 in the file src/support/environment.C. Yes, it was fairly easy with your hint. I put the epstopdf and convert scripts in their own directoy at the beginning of PATH. Shouldn't I do something else to connect them to epstopdf.exe in Miktex\texmf and C:\ImageMagick\convert.exe ? I don't have Tetex installed and I think not Cygwin's ImageMagick. It seems too easy! Looking forward for a working LyX/Cygwin ;-) -- Enrico Thanks for all your help and tremendous effort in figuring out a working installation. I think it is miraculous that you could figure out all those configure switches. Now when somebody asks about Cygwin and LyX they can be pointed to your Wiki page. I'm writing this as I wait for make to finish. Thar she blows! I had to copy lyx(-qt).exe to c:\cygwin\bin because it complained about missing cywin1.dll and cygz.dll Regards, Stephen
Re: LyX on Cygwin
- Original Message - From: "Enrico Forestieri" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <lyx-users@lists.lyx.org> Sent: Friday, February 24, 2006 6:29 AM Subject: Re: LyX on Cygwin On Fri, 24 Feb 2006 03:55:43 -0800, Stephen Harris wrote: Yes, it was fairly easy with your hint. I put the epstopdf and convert scripts in their own directoy at the beginning of PATH. Shouldn't I do something else to connect them to epstopdf.exe in Miktex\texmf and C:\ImageMagick\convert.exe ? I don't have Tetex installed and I think not Cygwin's ImageMagick. It seems too easy! You should do nothing apart assuring that they are in the system PATH which you can set through the "Advanced" tab in "Control Panel->System" or use path_prefix (see below). SH: I put C:\cygwin\bin in the PATH Thar she blows! I had to copy lyx(-qt).exe to c:\cygwin\bin because it complained about missing cywin1.dll and cygz.dll No, don't do that. Simply add C:\cygwin\bin to the PATH as explained above. You could set path_prefix as in the native version through LyX preferences. The path_prefix should be written in posix (cygwin) syntax and I suggest that you put as the first elements the following ones: /usr/local/bin:/usr/bin:/usr/X11R6/bin and then fill in whatever you like using ':' as a separator. In this way you can put the epstopdf and convert scripts in /usr/local/bin which is searched first. Once you filled in path_prefix in LyX as I suggested above, I think that you could also remove C:\cygwin\bin from the system PATH, but I have not checked it (Hmm... may be it doesn't work...) -- Enrico The View function doesn't work. It complains about missing TeX class "article" when I first load the .lyx document and C:\texmf~ is in my PATH. The Tex Information produces a window but it contains no information. I used mount -f C: /c (not mount -f C: /cygdrive/c ?) as advised. Path prefix had no entries which I thought was a bit strange. I've tried both of these in Path prefix C:/reader7/Reader/acrord32 /c/reader7/Reader/acrord32 I've tried both of these absolute paths in File formats Viewer C:/reader7/Reader/acrord32 /c/reader7/Reader/acrord32 originally it just said Viewer pdflatex, acrord32, but didn't work. The Working directory automatically generated by LyX is C:/Cygwin/.xemacs The tmp directory generated by LyX is C:/Cygwin/tmp I also tried putting C:/texmf/miktex/bin in Path prefix and also the path to article.cls which is in ~/.../base separated from each other with a : also :C:/reader7/etc I'm not sure what is broken because of being a Pre version. For instance Import Latex is missing, it just has text imports. The spellchecker starts checking the second misspelled word. Anyway your instructions are proven to work. A new user can search the archives and find clarifications in this thread. I've remembered to modify, apply, save, and Reconfigure. My favorite test file, sample.lyx, does convert eps and jpeg, Stephen
Re: LyX on Cygwin
On Fri, 24 Feb 2006 14:13:04 -0800, Stephen Harris wrote: > The View function doesn't work. It complains about missing > TeX class "article" when I first load the .lyx document and > C:\texmf~ is in my PATH. Try reconfiguring after adjusting path_prefix (see below). > The Tex Information produces a > window but it contains no information. Yes, I also see this, but then this also happens with 1.3.7. > I used mount -f C: /c (not mount -f C: /cygdrive/c ?) as advised. Correct. To see if that works try "ls /c" in a cygwin shell. > Path prefix had no entries which I thought was a bit strange. It is normal. In 1.3.7 entries are added by the windows installer. > I've tried both of these in Path prefix > C:/reader7/Reader/acrord32 > /c/reader7/Reader/acrord32 > > I've tried both of these absolute paths in File formats Viewer > C:/reader7/Reader/acrord32 > /c/reader7/Reader/acrord32 > originally it just said Viewer pdflatex, acrord32, but didn't work. Please *always* use posix syntax in path_prefix, i.e., /c/reader7/... and *not* C:/reader7/... > The Working directory automatically generated by LyX is > C:/Cygwin/.xemacs Uh? It seems that you have not set the HOME variable. LyX/Cygwin uses HOME instead of USERPROFILE. Perhaps I should patch the sources such that USERPROFILE is used as a fallback if HOME is not set. For the moment, you can fix this by adding the HOME var in the same way you add the PATH var but in the user section. Set HOME to a folder of your choice and then try launching LyX with the option "-dbg init" to see what it thinks your home_dir is. > The tmp directory generated by LyX is C:/Cygwin/tmp This is correct. > I also tried putting C:/texmf/miktex/bin in Path prefix > and also the path to article.cls which is in ~/.../base > separated from each other with a : also :C:/reader7/etc As I noted above, always use posix syntax in path_prefix, so write that as /c/texmf/miktex/bin:/c/reader7/etc The ':' char must only be used as a separator. Please try the following as path_prefix (I am assuming that your AcroRd32.exe is in C:\reader7\Reader\acrord32 and that you issued the "mount -f C: /c" command) /usr/local/bin:/usr/bin:/usr/X11R6/bin:/c/texmf/miktex/bin:/c/reader7/Reader/acrord32 After modifying path_prefix, save the preferences and *restart* LyX. > I'm not sure what is broken because of being a Pre version. > For instance Import Latex is missing, it just has text imports. This is a known issue when a version suffix is used (the configure script should be called with the option --version-suffix= but it is not). To fix this do the following in a cygwin shell: cd /usr/local/bin ln -s tex2lyx-1.4.0.exe tex2lyx and then reconfigure LyX. > The spellchecker starts checking the second misspelled word. This also is a known bug in LyX. > Anyway your instructions are proven to work. A new user > can search the archives and find clarifications in this thread. > I've remembered to modify, apply, save, and Reconfigure. > > My favorite test file, sample.lyx, does convert eps and jpeg, I think that you have a working copy of LyX. You should simply fix some glitches. -- Enrico
Re: LyX on Cygwin
- Original Message - From: "Enrico Forestieri" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <lyx-users@lists.lyx.org> Sent: Friday, February 24, 2006 4:33 PM Subject: Re: LyX on Cygwin On Fri, 24 Feb 2006 14:13:04 -0800, Stephen Harris wrote: The View function doesn't work. It complains about missing TeX class "article" when I first load the .lyx document and C:\texmf~ is in my PATH. Try reconfiguring after adjusting path_prefix (see below). SH: The rest of the error message is "LyX will not be able to produce output." The Tex Information produces a window but it contains no information. Yes, I also see this, but then this also happens with 1.3.7. Perhaps normal for Cygwin/Linux but you can see all these files and their paths with Uwe or Angus native LyXwin. Or with Mingw build of LyX1.4.0_pre3. It is how I used to check that LyX communicated with Miktex:texmf I used mount -f C: /c (not mount -f C: /cygdrive/c ?) as advised. Correct. To see if that works try "ls /c" in a cygwin shell. Yes I see lots of my stuff. When I use File->Open it still displays the path in terms of /cygdrive/c/ which makes me nervous. Path prefix had no entries which I thought was a bit strange. It is normal. In 1.3.7 entries are added by the windows installer. I've tried both of these in Path prefix C:/reader7/Reader/acrord32 /c/reader7/Reader/acrord32 I've tried both of these absolute paths in File formats Viewer C:/reader7/Reader/acrord32 /c/reader7/Reader/acrord32 originally it just said Viewer pdflatex, acrord32, but didn't work. Please *always* use posix syntax in path_prefix, i.e., /c/reader7/... and *not* C:/reader7/... Ok, the reason I tried both was because /c/reader7/Reader/acrord32 failed to enable the pdflatex Viewing function. The Working directory automatically generated by LyX is C:/Cygwin/.xemacs Uh? It seems that you have not set the HOME variable. LyX/Cygwin uses HOME instead of USERPROFILE. Perhaps I should patch the sources such that USERPROFILE is used as a fallback if HOME is not set. For the moment, you can fix this by adding the HOME var in the same way you add the PATH var but in the user section. Set HOME to a folder of your choice and then try launching LyX with the option "-dbg init" to see what it thinks your home_dir is. I used to have Xemacs for Cygwin installed. I set the HOME variable to C:\Cygwin\.xemacs for it. I now have another version of Xemacs set to HOME there also so if I change it I have to move init.el files etc. The tmp directory generated by LyX is C:/Cygwin/tmp This is correct. I also tried putting C:/texmf/miktex/bin in Path prefix and also the path to article.cls which is in ~/.../base separated from each other with a : also :C:/reader7/etc As I noted above, always use posix syntax in path_prefix, so write that as /c/texmf/miktex/bin:/c/reader7/etc The ':' char must only be used as a separator. Please try the following as path_prefix (I am assuming that your AcroRd32.exe is in C:\reader7\Reader\acrord32 and that you issued the "mount -f C: /c" command) /usr/local/bin:/usr/bin:/usr/X11R6/bin:/c/texmf/miktex/bin:/c/reader7/Reader/acrord32 Oops. No acrord32 is short for the acrord32.exe I just noticed this after trying it and it failed. So I tried :/c/reader7/Reader/ which didn't work. I just tried it without the trailing slash /, and it didn't work. I start LyX with an icon linked to C:\cygwin\usr\local\bin\LyX-1.4.0.exe and it gives me an error message "Locale en_US could not be set" which has never mattered in the past. My language is set to English in LyX. The Locale error follows after the "LyX will not be able to produce output." After modifying path_prefix, save the preferences and *restart* LyX. I did that. I did that, tried Reconfigure, closed and opened, to no avail. I'm not sure what is broken because of being a Pre version. For instance Import Latex is missing, it just has text imports. This is a known issue when a version suffix is used (the configure script should be called with the option --version-suffix= but it is not). To fix this do the following in a cygwin shell: cd /usr/local/bin ln -s tex2lyx-1.4.0.exe tex2lyx and then reconfigure LyX. By cracky it worked! I can now import Latex. Anyway your instructions are proven to work. A new user can search the archives and find clarifications in this thread. I've remembered to modify, apply, save, and Reconfigure. My favorite test file, sample.lyx, does convert eps and jpeg, I think that you have a working copy of LyX. You should simply fix some glitches. -- Enrico I've watched Reconfigure process. It says yes to finding pdflatex and acrord32 and gsview32. I don't have any Viewers, no DVI or Postscript. I added :/c/gs/gs8.51/bin:/c/ghostgum/gsview to Path prefix and turned on Instant Preview. No pre
Re: LyX on Cygwin
Stephen Harris [EMAIL PROTECTED] writes: SH: The qt3 install got further this time but failed with this error: -DQT_NO_STL -DQT_NO_COMPRESS -I/usr/local/src/qt3/mkspecs/cygwin-g++-win32 -DAVE_QCONFIG_CPP /usr/local/src/qt3/src/tools/qglobal.cpp In file included from /usr/local/src/qt3/src/tools/qglobal.cpp:38: /usr/local/src/qt3/mkspecs/cygwin-g++-win32/qplatformdefs.h:67:20: resolv.h: No such file or directory make: *** [qglobal.o] Error 1 Ok, you need to install the minires-devel cygwin package. This is one of the packages that I hoped not having forgotten... I am going to update the wiki page. Thank you for helping in sorting this out. SH: I have been using X-Win32 as my X server. In order to make our systems closer, I downloaded most of the X11 files and headers. No, no. X11 is not needed at all ;-) But I seem to remember something about xforms. Are they still needed even though the build is with qt3? I searched Cygwin and there were no hits for xforms. Is this required and how about xpm? http://savannah.nongnu.org/download/xforms/xforms-1.0.90.tar.gz Neither xforms is required. You need to have installed only the packages listed on the wiki page (well, with the addition of minires-devel ;-) ). -- Enrico
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: lyx-users@lists.lyx.org Sent: Thursday, February 23, 2006 6:15 AM Subject: Re: LyX on Cygwin Stephen Harris [EMAIL PROTECTED] writes: SH: The qt3 install got further this time but failed with this error: -DQT_NO_STL -DQT_NO_COMPRESS -I/usr/local/src/qt3/mkspecs/cygwin-g++-win32 -DAVE_QCONFIG_CPP /usr/local/src/qt3/src/tools/qglobal.cpp In file included from /usr/local/src/qt3/src/tools/qglobal.cpp:38: /usr/local/src/qt3/mkspecs/cygwin-g++-win32/qplatformdefs.h:67:20: resolv.h: No such file or directory make: *** [qglobal.o] Error 1 Ok, you need to install the minires-devel cygwin package. This is one of the packages that I hoped not having forgotten... I am going to update the wiki page. Thank you for helping in sorting this out. Enrico That did the trick, Qt3 configured! You are doing all the hard work! There is a Cygwin icon in the upper left-hand corner of the command window. I left-click on it and it opens a drop-down menu. Then I choose Edit-mark and drag the mouse cursor over all those lines of ./configure options. Then I choose Edit-copy and paste those lines into Notepad and save the file. If on the off chance a configure run should fail, at a later date one can copy line by line from Notepad into the Cygwin command window, using Edit-paste to insert those lines of configure options. It saves typing for those of us who don't like typing. I figure some new users might not know this gadgetry. Well, I might as well get on with this and deliver a report. The make went a ways and then failed with this error message: ream.o ./qbitarray.o ./qmap.o ./qgcache.o ./qtextcodec.o ./qutfcodec.o ./moc_yac c.o ./qfile_unix.o ./qdir_unix.o ./qfileinfo_unix.o -lkernel32 -luser32 -lgd i32 -lcomdlg32 -ladvapi32 -lshell32 -lole32 -loleaut32 -luuid -limm32 -lwinmm -l wsock32 -lwinspool -lopengl32 /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot open linker script file /usr/lib/qt3/mkspecs/cygwin-g++-win32/i386pe.x-no-rdata: No such file or directory collect2: ld returned 1 exit status make[2]: *** [../../bin/moc] Error 1 make[2]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3/src/moc' make[1]: *** [src-moc] Error 2 make[1]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3' SH: Do you have the same version, 3.4.4? Also I noticed that I don't have a path: /usr/lib/qt3 and I used the default. I wasn't sure what file to edit so I copied /cygwin/lib which contains a qt3 to be under /usr/lib/qt3/mkspecs though I don't have cygwin-g++-win32/i386pe.x-no-rdata What I have: Directory of C:\Cygwin\lib\qt3\mkspecs\cygwin-g++ 01/24/2006 10:21 AMDIR . 01/24/2006 10:21 AMDIR .. 08/11/2005 02:59 PM 2,194 qmake.conf 08/11/2005 02:59 PM 2,332 qplatformdefs.h 2 File(s) 4,526 bytes But I do have a .../mkspecs/cygwin-g++-win32/i386pe.x.-no-rdat C:\Cygwin\usr\local\src\qt3\mkspecs That file etc. didn't get copied over to the /lib directory by the script. So I made this .../i386pe.x.-no-rdat conform to the script, but no dice. Copied what I found to where the script said it looked and couldn't find. Next I notice C:\Cygwin\usr\lib\gcc\i686-pc-cygwin\3.4.4\include\c++\i686-pc-cygwin has no /bin and no ld. It just contains a directory called /bits So I made that conform to the script (mkdir bin and copied /bin files). Run /usr/bin/make confclean; set the Path and Qtdir again; run link_includes; run configure again with all options; edit all: # line; then /usr/bin/make; Returned same error: /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot open linker script file /usr/lib/qt3/mkspecs/cygwin-g++-win32/i386pe.x-no-rdata: No such file or directory collect2: ld returned 1 exit status make[2]: *** [../../bin/moc] Error 1 make[2]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3/src/moc' make[1]: *** [src-moc] Error 2 make[1]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3' Regards, Stephen
Re: LyX on Cygwin
Stephen Harris [EMAIL PROTECTED] writes: That did the trick, Qt3 configured! You are doing all the hard work! There is a Cygwin icon in the upper left-hand corner of the command window. I left-click on it and it opens a drop-down menu. Then I choose Edit-mark and drag the mouse cursor over all those lines of ./configure options. Then I choose Edit-copy and paste those lines into Notepad and save the file. If on the off chance a configure run should fail, at a later date one can copy line by line from Notepad into the Cygwin command window, using Edit-paste to insert those lines of configure options. It saves typing for those of us who don't like typing. I figure some new users might not know this gadgetry. If you use an rxvt window (look in the c:\cygwin\bin folder and double click on rxvt.exe) copy and paste is much simpler. In a windows application do a copy as usual and then in the rxvt window simply press the middle mouse button to paste. Conversely, in an rxvt window simply select what you want to copy (it is automatically copied in the windows clipboard) and than do a paste in a windows app. Well, I might as well get on with this and deliver a report. The make went a ways and then failed with this error message: ream.o ./qbitarray.o ./qmap.o ./qgcache.o ./qtextcodec.o ./qutfcodec.o ./moc_yac c.o ./qfile_unix.o ./qdir_unix.o ./qfileinfo_unix.o -lkernel32 -luser32 -lgd i32 -lcomdlg32 -ladvapi32 -lshell32 -lole32 -loleaut32 -luuid -limm32 -lwinmm -l wsock32 -lwinspool -lopengl32 /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot open linker script file /usr/lib/qt3/mkspecs/cygwin-g++-win32/i386pe.x-no-rdata: No such file or directory collect2: ld returned 1 exit status make[2]: *** [../../bin/moc] Error 1 make[2]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3/src/moc' make[1]: *** [src-moc] Error 2 make[1]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3' This is quite strange. Are you sure that you are not trying to build a dynamic library? My instructions are for building a static Qt library. I can't build a dynamic Qt because I only have 256 Mb of memory and the build stops with an out of memory error. In this case I can't be of much help... Check that you use the -static switch to configure. SH: Do you have the same version, 3.4.4? Yes, I have the latest gcc available in cygwin. Also I noticed that I don't have a path: /usr/lib/qt3 and I used the default. I wasn't sure what file to edit so I copied /cygwin/lib which contains a qt3 to be under /usr/lib/qt3/mkspecs though I don't have cygwin-g++-win32/i386pe.x-no-rdata What I have: Directory of C:\Cygwin\lib\qt3\mkspecs\cygwin-g++ 01/24/2006 10:21 AMDIR . 01/24/2006 10:21 AMDIR .. 08/11/2005 02:59 PM 2,194 qmake.conf 08/11/2005 02:59 PM 2,332 qplatformdefs.h 2 File(s) 4,526 bytes Uh, oh... have you installed the cygwin Qt package by chance? But I do have a .../mkspecs/cygwin-g++-win32/i386pe.x.-no-rdat C:\Cygwin\usr\local\src\qt3\mkspecs That file etc. didn't get copied over to the /lib directory by the script. So I made this .../i386pe.x.-no-rdat conform to the script, but no dice. Copied what I found to where the script said it looked and couldn't find. Well, you should need to do no more and no less than what I put on the wiki, otherwise it means that somenthing is going wrong... Next I notice C:\Cygwin\usr\lib\gcc\i686-pc-cygwin\3.4.4\include\c++\i686-pc-cygwin has no /bin and no ld. It just contains a directory called /bits So I made that conform to the script (mkdir bin and copied /bin files). Run /usr/bin/make confclean; set the Path and Qtdir again; run link_includes; run configure again with all options; edit all: # line; then /usr/bin/make; Returned same error: /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot open linker script file /usr/lib/qt3/mkspecs/cygwin-g++-win32/i386pe.x-no-rdata: No such file or directory collect2: ld returned 1 exit status make[2]: *** [../../bin/moc] Error 1 make[2]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3/src/moc' make[1]: *** [src-moc] Error 2 make[1]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3' I cannot understand from where that prefix /usr/lib/qt3 comes from. If you have installed the official cygwin Qt packages, perhaps this is a symptom of a sort of clashing. -- Enrico
Re: LyX on Cygwin
Stephen Harris [EMAIL PROTECTED] writes: SH: The qt3 install got further this time but failed with this error: -DQT_NO_STL -DQT_NO_COMPRESS -I/usr/local/src/qt3/mkspecs/cygwin-g++-win32 -DAVE_QCONFIG_CPP /usr/local/src/qt3/src/tools/qglobal.cpp In file included from /usr/local/src/qt3/src/tools/qglobal.cpp:38: /usr/local/src/qt3/mkspecs/cygwin-g++-win32/qplatformdefs.h:67:20: resolv.h: No such file or directory make: *** [qglobal.o] Error 1 Ok, you need to install the minires-devel cygwin package. This is one of the packages that I hoped not having forgotten... I am going to update the wiki page. Thank you for helping in sorting this out. SH: I have been using X-Win32 as my X server. In order to make our systems closer, I downloaded most of the X11 files and headers. No, no. X11 is not needed at all ;-) But I seem to remember something about xforms. Are they still needed even though the build is with qt3? I searched Cygwin and there were no hits for xforms. Is this required and how about xpm? http://savannah.nongnu.org/download/xforms/xforms-1.0.90.tar.gz Neither xforms is required. You need to have installed only the packages listed on the wiki page (well, with the addition of minires-devel ;-) ). -- Enrico
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: lyx-users@lists.lyx.org Sent: Thursday, February 23, 2006 6:15 AM Subject: Re: LyX on Cygwin Stephen Harris [EMAIL PROTECTED] writes: SH: The qt3 install got further this time but failed with this error: -DQT_NO_STL -DQT_NO_COMPRESS -I/usr/local/src/qt3/mkspecs/cygwin-g++-win32 -DAVE_QCONFIG_CPP /usr/local/src/qt3/src/tools/qglobal.cpp In file included from /usr/local/src/qt3/src/tools/qglobal.cpp:38: /usr/local/src/qt3/mkspecs/cygwin-g++-win32/qplatformdefs.h:67:20: resolv.h: No such file or directory make: *** [qglobal.o] Error 1 Ok, you need to install the minires-devel cygwin package. This is one of the packages that I hoped not having forgotten... I am going to update the wiki page. Thank you for helping in sorting this out. Enrico That did the trick, Qt3 configured! You are doing all the hard work! There is a Cygwin icon in the upper left-hand corner of the command window. I left-click on it and it opens a drop-down menu. Then I choose Edit-mark and drag the mouse cursor over all those lines of ./configure options. Then I choose Edit-copy and paste those lines into Notepad and save the file. If on the off chance a configure run should fail, at a later date one can copy line by line from Notepad into the Cygwin command window, using Edit-paste to insert those lines of configure options. It saves typing for those of us who don't like typing. I figure some new users might not know this gadgetry. Well, I might as well get on with this and deliver a report. The make went a ways and then failed with this error message: ream.o ./qbitarray.o ./qmap.o ./qgcache.o ./qtextcodec.o ./qutfcodec.o ./moc_yac c.o ./qfile_unix.o ./qdir_unix.o ./qfileinfo_unix.o -lkernel32 -luser32 -lgd i32 -lcomdlg32 -ladvapi32 -lshell32 -lole32 -loleaut32 -luuid -limm32 -lwinmm -l wsock32 -lwinspool -lopengl32 /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot open linker script file /usr/lib/qt3/mkspecs/cygwin-g++-win32/i386pe.x-no-rdata: No such file or directory collect2: ld returned 1 exit status make[2]: *** [../../bin/moc] Error 1 make[2]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3/src/moc' make[1]: *** [src-moc] Error 2 make[1]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3' SH: Do you have the same version, 3.4.4? Also I noticed that I don't have a path: /usr/lib/qt3 and I used the default. I wasn't sure what file to edit so I copied /cygwin/lib which contains a qt3 to be under /usr/lib/qt3/mkspecs though I don't have cygwin-g++-win32/i386pe.x-no-rdata What I have: Directory of C:\Cygwin\lib\qt3\mkspecs\cygwin-g++ 01/24/2006 10:21 AMDIR . 01/24/2006 10:21 AMDIR .. 08/11/2005 02:59 PM 2,194 qmake.conf 08/11/2005 02:59 PM 2,332 qplatformdefs.h 2 File(s) 4,526 bytes But I do have a .../mkspecs/cygwin-g++-win32/i386pe.x.-no-rdat C:\Cygwin\usr\local\src\qt3\mkspecs That file etc. didn't get copied over to the /lib directory by the script. So I made this .../i386pe.x.-no-rdat conform to the script, but no dice. Copied what I found to where the script said it looked and couldn't find. Next I notice C:\Cygwin\usr\lib\gcc\i686-pc-cygwin\3.4.4\include\c++\i686-pc-cygwin has no /bin and no ld. It just contains a directory called /bits So I made that conform to the script (mkdir bin and copied /bin files). Run /usr/bin/make confclean; set the Path and Qtdir again; run link_includes; run configure again with all options; edit all: # line; then /usr/bin/make; Returned same error: /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot open linker script file /usr/lib/qt3/mkspecs/cygwin-g++-win32/i386pe.x-no-rdata: No such file or directory collect2: ld returned 1 exit status make[2]: *** [../../bin/moc] Error 1 make[2]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3/src/moc' make[1]: *** [src-moc] Error 2 make[1]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3' Regards, Stephen
Re: LyX on Cygwin
Stephen Harris [EMAIL PROTECTED] writes: That did the trick, Qt3 configured! You are doing all the hard work! There is a Cygwin icon in the upper left-hand corner of the command window. I left-click on it and it opens a drop-down menu. Then I choose Edit-mark and drag the mouse cursor over all those lines of ./configure options. Then I choose Edit-copy and paste those lines into Notepad and save the file. If on the off chance a configure run should fail, at a later date one can copy line by line from Notepad into the Cygwin command window, using Edit-paste to insert those lines of configure options. It saves typing for those of us who don't like typing. I figure some new users might not know this gadgetry. If you use an rxvt window (look in the c:\cygwin\bin folder and double click on rxvt.exe) copy and paste is much simpler. In a windows application do a copy as usual and then in the rxvt window simply press the middle mouse button to paste. Conversely, in an rxvt window simply select what you want to copy (it is automatically copied in the windows clipboard) and than do a paste in a windows app. Well, I might as well get on with this and deliver a report. The make went a ways and then failed with this error message: ream.o ./qbitarray.o ./qmap.o ./qgcache.o ./qtextcodec.o ./qutfcodec.o ./moc_yac c.o ./qfile_unix.o ./qdir_unix.o ./qfileinfo_unix.o -lkernel32 -luser32 -lgd i32 -lcomdlg32 -ladvapi32 -lshell32 -lole32 -loleaut32 -luuid -limm32 -lwinmm -l wsock32 -lwinspool -lopengl32 /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot open linker script file /usr/lib/qt3/mkspecs/cygwin-g++-win32/i386pe.x-no-rdata: No such file or directory collect2: ld returned 1 exit status make[2]: *** [../../bin/moc] Error 1 make[2]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3/src/moc' make[1]: *** [src-moc] Error 2 make[1]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3' This is quite strange. Are you sure that you are not trying to build a dynamic library? My instructions are for building a static Qt library. I can't build a dynamic Qt because I only have 256 Mb of memory and the build stops with an out of memory error. In this case I can't be of much help... Check that you use the -static switch to configure. SH: Do you have the same version, 3.4.4? Yes, I have the latest gcc available in cygwin. Also I noticed that I don't have a path: /usr/lib/qt3 and I used the default. I wasn't sure what file to edit so I copied /cygwin/lib which contains a qt3 to be under /usr/lib/qt3/mkspecs though I don't have cygwin-g++-win32/i386pe.x-no-rdata What I have: Directory of C:\Cygwin\lib\qt3\mkspecs\cygwin-g++ 01/24/2006 10:21 AMDIR . 01/24/2006 10:21 AMDIR .. 08/11/2005 02:59 PM 2,194 qmake.conf 08/11/2005 02:59 PM 2,332 qplatformdefs.h 2 File(s) 4,526 bytes Uh, oh... have you installed the cygwin Qt package by chance? But I do have a .../mkspecs/cygwin-g++-win32/i386pe.x.-no-rdat C:\Cygwin\usr\local\src\qt3\mkspecs That file etc. didn't get copied over to the /lib directory by the script. So I made this .../i386pe.x.-no-rdat conform to the script, but no dice. Copied what I found to where the script said it looked and couldn't find. Well, you should need to do no more and no less than what I put on the wiki, otherwise it means that somenthing is going wrong... Next I notice C:\Cygwin\usr\lib\gcc\i686-pc-cygwin\3.4.4\include\c++\i686-pc-cygwin has no /bin and no ld. It just contains a directory called /bits So I made that conform to the script (mkdir bin and copied /bin files). Run /usr/bin/make confclean; set the Path and Qtdir again; run link_includes; run configure again with all options; edit all: # line; then /usr/bin/make; Returned same error: /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot open linker script file /usr/lib/qt3/mkspecs/cygwin-g++-win32/i386pe.x-no-rdata: No such file or directory collect2: ld returned 1 exit status make[2]: *** [../../bin/moc] Error 1 make[2]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3/src/moc' make[1]: *** [src-moc] Error 2 make[1]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3' I cannot understand from where that prefix /usr/lib/qt3 comes from. If you have installed the official cygwin Qt packages, perhaps this is a symptom of a sort of clashing. -- Enrico
Re: LyX on Cygwin
Stephen Harris <[EMAIL PROTECTED]> writes: > SH: The qt3 install got further this time but failed with this error: > > -DQT_NO_STL -DQT_NO_COMPRESS > -I/usr/local/src/qt3/mkspecs/cygwin-g++-win32 > -DAVE_QCONFIG_CPP /usr/local/src/qt3/src/tools/qglobal.cpp > In file included from /usr/local/src/qt3/src/tools/qglobal.cpp:38: > /usr/local/src/qt3/mkspecs/cygwin-g++-win32/qplatformdefs.h:67:20: resolv.h: > No such file or directory > make: *** [qglobal.o] Error 1 Ok, you need to install the minires-devel cygwin package. This is one of the packages that I hoped not having forgotten... I am going to update the wiki page. Thank you for helping in sorting this out. > SH: I have been using X-Win32 as my X server. In order to make > our systems closer, I downloaded most of the X11 files and headers. No, no. X11 is not needed at all ;-) > But I seem to remember something about xforms. Are they still needed > even though the build is with qt3? I searched Cygwin and there were > no hits for xforms. Is this required and how about xpm? > http://savannah.nongnu.org/download/xforms/xforms-1.0.90.tar.gz Neither xforms is required. You need to have installed only the packages listed on the wiki page (well, with the addition of minires-devel ;-) ). -- Enrico
Re: LyX on Cygwin
- Original Message - From: "Enrico Forestieri" <[EMAIL PROTECTED]> To: <lyx-users@lists.lyx.org> Sent: Thursday, February 23, 2006 6:15 AM Subject: Re: LyX on Cygwin Stephen Harris <[EMAIL PROTECTED]> writes: SH: The qt3 install got further this time but failed with this error: -DQT_NO_STL -DQT_NO_COMPRESS -I/usr/local/src/qt3/mkspecs/cygwin-g++-win32 -DAVE_QCONFIG_CPP /usr/local/src/qt3/src/tools/qglobal.cpp In file included from /usr/local/src/qt3/src/tools/qglobal.cpp:38: /usr/local/src/qt3/mkspecs/cygwin-g++-win32/qplatformdefs.h:67:20: resolv.h: No such file or directory make: *** [qglobal.o] Error 1 Ok, you need to install the minires-devel cygwin package. This is one of the packages that I hoped not having forgotten... I am going to update the wiki page. Thank you for helping in sorting this out. Enrico That did the trick, Qt3 configured! You are doing all the hard work! There is a Cygwin icon in the upper left-hand corner of the command window. I left-click on it and it opens a drop-down menu. Then I choose Edit->mark and drag the mouse cursor over all those lines of ./configure options. Then I choose Edit->copy and paste those lines into Notepad and save the file. If on the off chance a configure run should fail, at a later date one can copy line by line from Notepad into the Cygwin command window, using Edit->paste to insert those lines of configure options. It saves typing for those of us who don't like typing. I figure some new users might not know this gadgetry. Well, I might as well get on with this and deliver a report. The make went a ways and then failed with this error message: ream.o ./qbitarray.o ./qmap.o ./qgcache.o ./qtextcodec.o ./qutfcodec.o ./moc_yac c.o ./qfile_unix.o ./qdir_unix.o ./qfileinfo_unix.o -lkernel32 -luser32 -lgd i32 -lcomdlg32 -ladvapi32 -lshell32 -lole32 -loleaut32 -luuid -limm32 -lwinmm -l wsock32 -lwinspool -lopengl32 /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot open linker script file /usr/lib/qt3/mkspecs/cygwin-g++-win32/i386pe.x-no-rdata: No such file or directory collect2: ld returned 1 exit status make[2]: *** [../../bin/moc] Error 1 make[2]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3/src/moc' make[1]: *** [src-moc] Error 2 make[1]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3' SH: Do you have the same version, 3.4.4? Also I noticed that I don't have a path: /usr/lib/qt3 and I used the default. I wasn't sure what file to edit so I copied /cygwin/lib which contains a qt3 to be under /usr/lib/qt3/mkspecs though I don't have cygwin-g++-win32/i386pe.x-no-rdata What I have: Directory of C:\Cygwin\lib\qt3\mkspecs\cygwin-g++ 01/24/2006 10:21 AM . 01/24/2006 10:21 AM .. 08/11/2005 02:59 PM 2,194 qmake.conf 08/11/2005 02:59 PM 2,332 qplatformdefs.h 2 File(s) 4,526 bytes But I do have a .../mkspecs/cygwin-g++-win32/i386pe.x.-no-rdat C:\Cygwin\usr\local\src\qt3\mkspecs That file etc. didn't get copied over to the /lib directory by the script. So I made this .../i386pe.x.-no-rdat conform to the script, but no dice. Copied what I found to where the script said it looked and couldn't find. Next I notice C:\Cygwin\usr\lib\gcc\i686-pc-cygwin\3.4.4\include\c++\i686-pc-cygwin has no /bin and no ld. It just contains a directory called /bits So I made that conform to the script (mkdir bin and copied /bin files). Run /usr/bin/make confclean; set the Path and Qtdir again; run link_includes; run configure again with all options; edit all: # line; then /usr/bin/make; Returned same error: /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot open linker script file /usr/lib/qt3/mkspecs/cygwin-g++-win32/i386pe.x-no-rdata: No such file or directory collect2: ld returned 1 exit status make[2]: *** [../../bin/moc] Error 1 make[2]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3/src/moc' make[1]: *** [src-moc] Error 2 make[1]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3' Regards, Stephen
Re: LyX on Cygwin
Stephen Harris <[EMAIL PROTECTED]> writes: > That did the trick, Qt3 configured! You are doing all the hard work! > > There is a Cygwin icon in the upper left-hand corner of the command > window. I left-click on it and it opens a drop-down menu. Then I > choose Edit->mark and drag the mouse cursor over all those lines of > ./configure options. Then I choose Edit->copy and paste those > lines into Notepad and save the file. If on the off chance a configure > run should fail, at a later date one can copy line by line from Notepad > into the Cygwin command window, using Edit->paste to insert those > lines of configure options. It saves typing for those of us who don't > like typing. I figure some new users might not know this gadgetry. If you use an rxvt window (look in the c:\cygwin\bin folder and double click on rxvt.exe) copy and paste is much simpler. In a windows application do a copy as usual and then in the rxvt window simply press the middle mouse button to paste. Conversely, in an rxvt window simply select what you want to copy (it is automatically copied in the windows clipboard) and than do a paste in a windows app. > Well, I might as well get on with this and deliver a report. The make > went a ways and then failed with this error message: > > ream.o ./qbitarray.o ./qmap.o ./qgcache.o ./qtextcodec.o ./qutfcodec.o > ./moc_yac > c.o ./qfile_unix.o ./qdir_unix.o > ./qfileinfo_unix.o -lkernel32 -luser32 -lgd > i32 -lcomdlg32 -ladvapi32 -lshell32 -lole32 -loleaut32 -luuid -limm32 -lwinmm > -l > wsock32 -lwinspool -lopengl32 > /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot > open > linker script file /usr/lib/qt3/mkspecs/cygwin-g++-win32/i386pe.x-no-rdata: > No > such file or directory > collect2: ld returned 1 exit status > make[2]: *** [../../bin/moc] Error 1 > make[2]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3/src/moc' > make[1]: *** [src-moc] Error 2 > make[1]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3' This is quite strange. Are you sure that you are not trying to build a dynamic library? My instructions are for building a static Qt library. I can't build a dynamic Qt because I only have 256 Mb of memory and the build stops with an out of memory error. In this case I can't be of much help... Check that you use the -static switch to configure. > SH: Do you have the same version, 3.4.4? Yes, I have the latest gcc available in cygwin. > Also I noticed that I don't have a path: /usr/lib/qt3 and I used the > default. > I wasn't sure what file to edit so I copied /cygwin/lib which contains a qt3 > to be under /usr/lib/qt3/mkspecs though I don't have > cygwin-g++-win32/i386pe.x-no-rdata > > What I have: > > Directory of C:\Cygwin\lib\qt3\mkspecs\cygwin-g++ > > 01/24/2006 10:21 AM . > 01/24/2006 10:21 AM .. > 08/11/2005 02:59 PM 2,194 qmake.conf > 08/11/2005 02:59 PM 2,332 qplatformdefs.h >2 File(s) 4,526 bytes Uh, oh... have you installed the cygwin Qt package by chance? > But I do have a .../mkspecs/cygwin-g++-win32/i386pe.x.-no-rdat > C:\Cygwin\usr\local\src\qt3\mkspecs > > That file etc. didn't get copied over to the /lib directory by the script. > So I made this .../i386pe.x.-no-rdat conform to the script, but no dice. > Copied what I found to where the script said it looked and couldn't find. Well, you should need to do no more and no less than what I put on the wiki, otherwise it means that somenthing is going wrong... > Next I notice > C:\Cygwin\usr\lib\gcc\i686-pc-cygwin\3.4.4\include\c++\i686-pc-cygwin > has no /bin and no ld. It just contains a directory called /bits > So I made that conform to the script (mkdir bin and copied /bin files). > Run /usr/bin/make confclean; set the Path and Qtdir again; run > link_includes; > run configure again with all options; edit all: # line; then /usr/bin/make; > > Returned same error: > /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot > open > linker script file /usr/lib/qt3/mkspecs/cygwin-g++-win32/i386pe.x-no-rdata: > No > such file or directory > collect2: ld returned 1 exit status > make[2]: *** [../../bin/moc] Error 1 > make[2]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3/src/moc' > make[1]: *** [src-moc] Error 2 > make[1]: Leaving directory `/cygdrive/c/cygwin/usr/local/src/qt3' I cannot understand from where that prefix "/usr/lib/qt3" comes from. If you have installed the official cygwin Qt packages, perhaps this is a symptom of a sort of clashing. -- Enrico
Re: LyX on Cygwin
Stephen Harris [EMAIL PROTECTED] writes: I did not succeed in compiling Qt. I got the files in the right directory with cvs, but the ./configure failed quickly with the error make: *** [project.o] Error 1 qmake failed to build. Aborting Probably this is because the qt3/include dir should be populated first. I had that dir already populated by a previous MinGW build, so I forgot to add the instructions to do so. I have updated the Qt patches and the howto at http://wiki.lyx.org/LyX/LyXOnCygwin Is this line correctly typed? ./configure -platform cygwin-g++-win32 -v -release -static also I didn't put a backslash \, at the end of the continued configure lines of switches, but that didn't seem to matter. Yes it is. You can type all switches in a very long line. I am not motivated to put much effort into troubleshooting as I wanted to look at Pre5 now, but the final release is due soon. ;-) -- Enrico
Re: LyX on Cygwin
On Thu, 23 Feb 2006 00:33:06 + (UTC), Enrico Forestieri [EMAIL PROTECTED] said: Enrico Stephen Harris [EMAIL PROTECTED] writes: I did not succeed in compiling Qt. I got the files in the right directory with cvs, but the ./configure failed quickly with the error make: *** [project.o] Error 1 qmake failed to build. Aborting Enrico Probably this is because the qt3/include dir should be Enrico populated first. I had that dir already populated by a Enrico previous MinGW build, so I forgot to add the instructions to Enrico do so. I have updated the Qt patches and the howto at Enrico http://wiki.lyx.org/LyX/LyXOnCygwin Enrico -- Enrico - SH: Ok, I will give it another try. I did notice an apparent discrepancy in the instuctions from the LyXonCygwin page: - In this howto all examples are shown for tcsh, but it is trivial to change them for bash. Mainly, it is simply a matter of substituting export XXX=YYY in place of setenv XXX YYY (or simply use tcsh instead of bash). -- If your Qt source tree is not in /usr/local/src/qt3, you should now modify as appropriate the following line export QTDIR=/usr/local/src/qt3 at the very start of the following sh scripts: config.tests/unix/endian.test config.tests/unix/ipv6.test config.tests/unix/largefile.test config.tests/unix/ptrsize.test config.tests/unix/stl.test - SH: It appears to me that export QTDIR=/usr/local/src/qt3 is written in bash syntax rather than all tcsh syntax? I did try the tcsh shell and I liked how it displayed the contents (directory vs. file). I have a Mingw directory of Qt3 from LyX140-pre3 already but I will follow the instructions on the webpage as a proof of concept (hope). I'm (un?)fortunately perfectionistic. Supercitelfully yours, Stephen
Re: LyX on Cygwin
Stephen Harris [EMAIL PROTECTED] writes: SH: Ok, I will give it another try. I did notice an apparent discrepancy in the instuctions from the LyXonCygwin page: - In this howto all examples are shown for tcsh, but it is trivial to change them for bash. Mainly, it is simply a matter of substituting export XXX=YYY in place of setenv XXX YYY (or simply use tcsh instead of bash). -- If your Qt source tree is not in /usr/local/src/qt3, you should now modify as appropriate the following line export QTDIR=/usr/local/src/qt3 at the very start of the following sh scripts: config.tests/unix/endian.test config.tests/unix/ipv6.test config.tests/unix/largefile.test config.tests/unix/ptrsize.test config.tests/unix/stl.test - SH: It appears to me that export QTDIR=/usr/local/src/qt3 is written in bash syntax rather than all tcsh syntax? Yes, that's correct. Indeed, those scripts are Bourne shell scripts. I use tcsh for interactive working, but sh (or bash) is better for scripting. So, what you should enter on the command line is in tcsh syntax, whereas the scripts are in sh syntax. I did try the tcsh shell and I liked how it displayed the contents (directory vs. file). I have a Mingw directory of Qt3 from LyX140-pre3 already but I will follow the instructions on the webpage as a proof of concept (hope). I'm (un?)fortunately perfectionistic. I think that you are right. I myself followed those instructions and downloaded again from scratch the Qt sources, thus finding the problem of the not populated include dir. Had you used your existing Qt3 directory you would have had no problems ;-) Please, download again the qt3-cygwin.patch file as I updated it. Applying that patch you will find the link_includes script in the bin directory. This is the script that should be run before the configure command to populate the include dir. You should also revert the previous patch. I think that it can be done using the -R switch to the patch command, but perhaps it is better if you simply delete all patched files and then do a cvs update to have them freshly restored. Also, pay attention to the updated instructions on the wiki as I added a switch to the tar command used to copy the includes such that it dereferences the symlinks created by link_includes. -- Enrico
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: lyx-users@lists.lyx.org Sent: Wednesday, February 22, 2006 8:10 PM Subject: Re: LyX on Cygwin Stephen Harris [EMAIL PROTECTED] writes: SH: Ok, I will give it another try. I did notice an apparent discrepancy in the instuctions from the LyXonCygwin page: I have a Mingw directory of Qt3 from LyX140-pre3 already but I will follow the instructions on the webpage as a proof of concept (hope). I'm (un?)fortunately perfectionistic. I think that you are right. I myself followed those instructions and downloaded again from scratch the Qt sources, thus finding the problem of the not populated include dir. Had you used your existing Qt3 directory you would have had no problems ;-) Please, download again the qt3-cygwin.patch file as I updated it. Applying that patch you will find the link_includes script in the bin directory. This is the script that should be run before the configure command to populate the include dir. SH: I removed the entire qt3 directory and started over. You should also revert the previous patch. I think that it can be done using the -R switch to the patch command, but perhaps it is better if you simply delete all patched files and then do a cvs update to have them freshly restored. SH: I downloaded the patch and it apparently worked. Also, pay attention to the updated instructions on the wiki as I added a switch to the tar command used to copy the includes such that it dereferences the symlinks created by link_includes. -- Enrico SH: The qt3 install got further this time but failed with this error: -DQT_NO_STL -DQT_NO_COMPRESS -I/usr/local/src/qt3/mkspecs/cygwin-g++-win32 -DAVE_QCONFIG_CPP /usr/local/src/qt3/src/tools/qglobal.cpp In file included from /usr/local/src/qt3/src/tools/qglobal.cpp:38: /usr/local/src/qt3/mkspecs/cygwin-g++-win32/qplatformdefs.h:67:20: resolv.h: No such file or directory make: *** [qglobal.o] Error 1 SH: I have been using X-Win32 as my X server. In order to make our systems closer, I downloaded most of the X11 files and headers. But I seem to remember something about xforms. Are they still needed even though the build is with qt3? I searched Cygwin and there were no hits for xforms. Is this required and how about xpm? http://savannah.nongnu.org/download/xforms/xforms-1.0.90.tar.gz I may try this again with my old qt3 directory as the QTsrcdir. Regards, Stephen
Re: LyX on Cygwin
Stephen Harris [EMAIL PROTECTED] writes: I did not succeed in compiling Qt. I got the files in the right directory with cvs, but the ./configure failed quickly with the error make: *** [project.o] Error 1 qmake failed to build. Aborting Probably this is because the qt3/include dir should be populated first. I had that dir already populated by a previous MinGW build, so I forgot to add the instructions to do so. I have updated the Qt patches and the howto at http://wiki.lyx.org/LyX/LyXOnCygwin Is this line correctly typed? ./configure -platform cygwin-g++-win32 -v -release -static also I didn't put a backslash \, at the end of the continued configure lines of switches, but that didn't seem to matter. Yes it is. You can type all switches in a very long line. I am not motivated to put much effort into troubleshooting as I wanted to look at Pre5 now, but the final release is due soon. ;-) -- Enrico
Re: LyX on Cygwin
On Thu, 23 Feb 2006 00:33:06 + (UTC), Enrico Forestieri [EMAIL PROTECTED] said: Enrico Stephen Harris [EMAIL PROTECTED] writes: I did not succeed in compiling Qt. I got the files in the right directory with cvs, but the ./configure failed quickly with the error make: *** [project.o] Error 1 qmake failed to build. Aborting Enrico Probably this is because the qt3/include dir should be Enrico populated first. I had that dir already populated by a Enrico previous MinGW build, so I forgot to add the instructions to Enrico do so. I have updated the Qt patches and the howto at Enrico http://wiki.lyx.org/LyX/LyXOnCygwin Enrico -- Enrico - SH: Ok, I will give it another try. I did notice an apparent discrepancy in the instuctions from the LyXonCygwin page: - In this howto all examples are shown for tcsh, but it is trivial to change them for bash. Mainly, it is simply a matter of substituting export XXX=YYY in place of setenv XXX YYY (or simply use tcsh instead of bash). -- If your Qt source tree is not in /usr/local/src/qt3, you should now modify as appropriate the following line export QTDIR=/usr/local/src/qt3 at the very start of the following sh scripts: config.tests/unix/endian.test config.tests/unix/ipv6.test config.tests/unix/largefile.test config.tests/unix/ptrsize.test config.tests/unix/stl.test - SH: It appears to me that export QTDIR=/usr/local/src/qt3 is written in bash syntax rather than all tcsh syntax? I did try the tcsh shell and I liked how it displayed the contents (directory vs. file). I have a Mingw directory of Qt3 from LyX140-pre3 already but I will follow the instructions on the webpage as a proof of concept (hope). I'm (un?)fortunately perfectionistic. Supercitelfully yours, Stephen
Re: LyX on Cygwin
Stephen Harris [EMAIL PROTECTED] writes: SH: Ok, I will give it another try. I did notice an apparent discrepancy in the instuctions from the LyXonCygwin page: - In this howto all examples are shown for tcsh, but it is trivial to change them for bash. Mainly, it is simply a matter of substituting export XXX=YYY in place of setenv XXX YYY (or simply use tcsh instead of bash). -- If your Qt source tree is not in /usr/local/src/qt3, you should now modify as appropriate the following line export QTDIR=/usr/local/src/qt3 at the very start of the following sh scripts: config.tests/unix/endian.test config.tests/unix/ipv6.test config.tests/unix/largefile.test config.tests/unix/ptrsize.test config.tests/unix/stl.test - SH: It appears to me that export QTDIR=/usr/local/src/qt3 is written in bash syntax rather than all tcsh syntax? Yes, that's correct. Indeed, those scripts are Bourne shell scripts. I use tcsh for interactive working, but sh (or bash) is better for scripting. So, what you should enter on the command line is in tcsh syntax, whereas the scripts are in sh syntax. I did try the tcsh shell and I liked how it displayed the contents (directory vs. file). I have a Mingw directory of Qt3 from LyX140-pre3 already but I will follow the instructions on the webpage as a proof of concept (hope). I'm (un?)fortunately perfectionistic. I think that you are right. I myself followed those instructions and downloaded again from scratch the Qt sources, thus finding the problem of the not populated include dir. Had you used your existing Qt3 directory you would have had no problems ;-) Please, download again the qt3-cygwin.patch file as I updated it. Applying that patch you will find the link_includes script in the bin directory. This is the script that should be run before the configure command to populate the include dir. You should also revert the previous patch. I think that it can be done using the -R switch to the patch command, but perhaps it is better if you simply delete all patched files and then do a cvs update to have them freshly restored. Also, pay attention to the updated instructions on the wiki as I added a switch to the tar command used to copy the includes such that it dereferences the symlinks created by link_includes. -- Enrico
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: lyx-users@lists.lyx.org Sent: Wednesday, February 22, 2006 8:10 PM Subject: Re: LyX on Cygwin Stephen Harris [EMAIL PROTECTED] writes: SH: Ok, I will give it another try. I did notice an apparent discrepancy in the instuctions from the LyXonCygwin page: I have a Mingw directory of Qt3 from LyX140-pre3 already but I will follow the instructions on the webpage as a proof of concept (hope). I'm (un?)fortunately perfectionistic. I think that you are right. I myself followed those instructions and downloaded again from scratch the Qt sources, thus finding the problem of the not populated include dir. Had you used your existing Qt3 directory you would have had no problems ;-) Please, download again the qt3-cygwin.patch file as I updated it. Applying that patch you will find the link_includes script in the bin directory. This is the script that should be run before the configure command to populate the include dir. SH: I removed the entire qt3 directory and started over. You should also revert the previous patch. I think that it can be done using the -R switch to the patch command, but perhaps it is better if you simply delete all patched files and then do a cvs update to have them freshly restored. SH: I downloaded the patch and it apparently worked. Also, pay attention to the updated instructions on the wiki as I added a switch to the tar command used to copy the includes such that it dereferences the symlinks created by link_includes. -- Enrico SH: The qt3 install got further this time but failed with this error: -DQT_NO_STL -DQT_NO_COMPRESS -I/usr/local/src/qt3/mkspecs/cygwin-g++-win32 -DAVE_QCONFIG_CPP /usr/local/src/qt3/src/tools/qglobal.cpp In file included from /usr/local/src/qt3/src/tools/qglobal.cpp:38: /usr/local/src/qt3/mkspecs/cygwin-g++-win32/qplatformdefs.h:67:20: resolv.h: No such file or directory make: *** [qglobal.o] Error 1 SH: I have been using X-Win32 as my X server. In order to make our systems closer, I downloaded most of the X11 files and headers. But I seem to remember something about xforms. Are they still needed even though the build is with qt3? I searched Cygwin and there were no hits for xforms. Is this required and how about xpm? http://savannah.nongnu.org/download/xforms/xforms-1.0.90.tar.gz I may try this again with my old qt3 directory as the QTsrcdir. Regards, Stephen
Re: LyX on Cygwin
Stephen Harris <[EMAIL PROTECTED]> writes: > I did not succeed in compiling Qt. I got the files in the right > directory with cvs, but the ./configure failed quickly with the error > > make: *** [project.o] Error 1 > qmake failed to build. Aborting Probably this is because the qt3/include dir should be populated first. I had that dir already populated by a previous MinGW build, so I forgot to add the instructions to do so. I have updated the Qt patches and the howto at http://wiki.lyx.org/LyX/LyXOnCygwin > Is this line correctly typed? > ./configure -platform cygwin-g++-win32 -v -release -static > also I didn't put a backslash \, at the end of the continued > configure lines of switches, but that didn't seem to matter. Yes it is. You can type all switches in a very long line. > I am not motivated to put much effort into troubleshooting as > I wanted to look at Pre5 now, but the final release is due soon. ;-) -- Enrico
Re: LyX on Cygwin
> On Thu, 23 Feb 2006 00:33:06 + (UTC), Enrico Forestieri <[EMAIL > PROTECTED]> said: Enrico> Stephen Harris <[EMAIL PROTECTED]> writes: >> I did not succeed in compiling Qt. I got the files in the right >> directory with cvs, but the ./configure failed quickly with the >> error >> >> make: *** [project.o] Error 1 qmake failed to build. Aborting Enrico> Probably this is because the qt3/include dir should be Enrico> populated first. I had that dir already populated by a Enrico> previous MinGW build, so I forgot to add the instructions to Enrico> do so. I have updated the Qt patches and the howto at Enrico> http://wiki.lyx.org/LyX/LyXOnCygwin Enrico> -- Enrico - SH: Ok, I will give it another try. I did notice an apparent discrepancy in the instuctions from the LyXonCygwin page: - In this howto all examples are shown for tcsh, but it is trivial to change them for bash. Mainly, it is simply a matter of substituting "export XXX=YYY" in place of "setenv XXX YYY" (or simply use tcsh instead of bash). -- If your Qt source tree is not in /usr/local/src/qt3, you should now modify as appropriate the following line export QTDIR=/usr/local/src/qt3 at the very start of the following sh scripts: config.tests/unix/endian.test config.tests/unix/ipv6.test config.tests/unix/largefile.test config.tests/unix/ptrsize.test config.tests/unix/stl.test - SH: It appears to me that "export QTDIR=/usr/local/src/qt3" is written in bash syntax rather than "all" tcsh syntax? I did try the tcsh shell and I liked how it displayed the contents (directory vs. file). I have a Mingw directory of Qt3 from LyX140-pre3 already but I will follow the instructions on the webpage as a proof of concept (hope). I'm (un?)fortunately perfectionistic. Supercitelfully yours, Stephen
Re: LyX on Cygwin
Stephen Harris <[EMAIL PROTECTED]> writes: > SH: Ok, I will give it another try. I did notice an apparent > discrepancy in the instuctions from the LyXonCygwin page: > > - > > In this howto all examples are shown for tcsh, but it is > trivial to change them for bash. Mainly, it is simply a > matter of substituting "export XXX=YYY" in place of > "setenv XXX YYY" (or simply use tcsh instead of bash). > > -- > > If your Qt source tree is not in /usr/local/src/qt3, you > should now modify as appropriate the following line > > export QTDIR=/usr/local/src/qt3 > at the very start of the following sh scripts: > config.tests/unix/endian.test > config.tests/unix/ipv6.test > config.tests/unix/largefile.test > config.tests/unix/ptrsize.test > config.tests/unix/stl.test > - > > SH: It appears to me that "export QTDIR=/usr/local/src/qt3" > is written in bash syntax rather than "all" tcsh syntax? Yes, that's correct. Indeed, those scripts are Bourne shell scripts. I use tcsh for interactive working, but sh (or bash) is better for scripting. So, what you should enter on the command line is in tcsh syntax, whereas the scripts are in sh syntax. > I did try the tcsh shell and I liked how it displayed the > contents (directory vs. file). > > I have a Mingw directory of Qt3 from LyX140-pre3 already > but I will follow the instructions on the webpage as a > proof of concept (hope). I'm (un?)fortunately perfectionistic. I think that you are right. I myself followed those instructions and downloaded again from scratch the Qt sources, thus finding the problem of the not populated include dir. Had you used your existing Qt3 directory you would have had no problems ;-) Please, download again the qt3-cygwin.patch file as I updated it. Applying that patch you will find the link_includes script in the bin directory. This is the script that should be run before the configure command to populate the include dir. You should also revert the previous patch. I think that it can be done using the -R switch to the patch command, but perhaps it is better if you simply delete all patched files and then do a "cvs update" to have them freshly restored. Also, pay attention to the updated instructions on the wiki as I added a switch to the tar command used to copy the includes such that it dereferences the symlinks created by link_includes. -- Enrico
Re: LyX on Cygwin
- Original Message - From: "Enrico Forestieri" <[EMAIL PROTECTED]> To: <lyx-users@lists.lyx.org> Sent: Wednesday, February 22, 2006 8:10 PM Subject: Re: LyX on Cygwin Stephen Harris <[EMAIL PROTECTED]> writes: SH: Ok, I will give it another try. I did notice an apparent discrepancy in the instuctions from the LyXonCygwin page: I have a Mingw directory of Qt3 from LyX140-pre3 already but I will follow the instructions on the webpage as a proof of concept (hope). I'm (un?)fortunately perfectionistic. I think that you are right. I myself followed those instructions and downloaded again from scratch the Qt sources, thus finding the problem of the not populated include dir. Had you used your existing Qt3 directory you would have had no problems ;-) Please, download again the qt3-cygwin.patch file as I updated it. Applying that patch you will find the link_includes script in the bin directory. This is the script that should be run before the configure command to populate the include dir. SH: I removed the entire qt3 directory and started over. You should also revert the previous patch. I think that it can be done using the -R switch to the patch command, but perhaps it is better if you simply delete all patched files and then do a "cvs update" to have them freshly restored. SH: I downloaded the patch and it apparently worked. Also, pay attention to the updated instructions on the wiki as I added a switch to the tar command used to copy the includes such that it dereferences the symlinks created by link_includes. -- Enrico SH: The qt3 install got further this time but failed with this error: -DQT_NO_STL -DQT_NO_COMPRESS -I/usr/local/src/qt3/mkspecs/cygwin-g++-win32 -DAVE_QCONFIG_CPP /usr/local/src/qt3/src/tools/qglobal.cpp In file included from /usr/local/src/qt3/src/tools/qglobal.cpp:38: /usr/local/src/qt3/mkspecs/cygwin-g++-win32/qplatformdefs.h:67:20: resolv.h: No such file or directory make: *** [qglobal.o] Error 1 SH: I have been using X-Win32 as my X server. In order to make our systems closer, I downloaded most of the X11 files and headers. But I seem to remember something about xforms. Are they still needed even though the build is with qt3? I searched Cygwin and there were no hits for xforms. Is this required and how about xpm? http://savannah.nongnu.org/download/xforms/xforms-1.0.90.tar.gz I may try this again with my old qt3 directory as the QTsrcdir. Regards, Stephen
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: lyx-users@lists.lyx.org Sent: Friday, February 17, 2006 1:45 PM Subject: Re: LyX on Cygwin Stephen Harris [EMAIL PROTECTED] writes: The Pre5 doesn't have a configure file to execute the several ./configure switches in Enrico's Howto. Are you sure? The lyx-1.4.0pre5.tar.bz2 archive I downloaded from ftp://ftp.devel.lyx.org/pub/lyx/pre/ had one ... Yes, I am sure that in both lyx-1.4.0pre5.tar.bz2 (or tar.gz) there is no configure file. Nor is there an autogen.sh file nor a configure.ac. All of those files are missing, the ones you would normally expect to see in lyx-devel. Just to be sure I have downloaded again ftp://ftp.devel.lyx.org/pub/lyx/pre/lyx-1.4.0pre5.tar.bz2 and those files are there... cd lyx-1.4.0pre5 ./autogen.sh I don't see how it is possible to run this command as the files are non-existent. The files can be found in the cvs lyx-devel directory, but your instructions don't say to use cvs for obtaining installation files which don't come as bz2 or tar.gz you say Unpack lyx-1.4.x.tar.bz2 in /usr/local/src (replace x ^ to match your archive name) But the files *are* there... Anyway, things do not change with a cvs version, simply replace lyx-1.4.x with lyx-devel ;-) I've already had the experience of not being able to compile the cvs files, but I was able to compile Lyx1.4.0pre3, so it is by no means certain that one can just adapt your configure switches to the current cvs files. Try it, it should work. Lyx1.4.0pre3 came with about 20 files not contained in Lyx1.4.0pre5. Since you say the files were contained The lyx-1.4.0pre5.tar.bz2 archive I downloaded ... had one it seems that somebody has deleted files from lyx-1.4.0pre5.tar.bz2 and tar.gz for that matter and repackaged. (no configure, configure.ac or autogen.sh plus many others) I think that nobody did that ;-) It may be a problem with the software you used to unpack the archive. Try using the cygwin tools: cd /usr/local/src tar jxvf /path/to/lyx-1.4.0pre5.tar.bz2 or tar zxvf /path/to/lyx-1.4.0pre5.tar.gz if you downloaded the .gz version. The problem I reported remains just as murky, Don't be desperate, try again. I am sure it is not so difficult. Did you succeeded in compiling Qt? -- Enrico I unpacked the archives with WinRar which is supposed to work but apparently didn't because using tar worked to display the files. I did not succeed in compiling Qt. I got the files in the right directory with cvs, but the ./configure failed quickly with the error make: *** [project.o] Error 1 qmake failed to build. Aborting Is this line correctly typed? ./configure -platform cygwin-g++-win32 -v -release -static also I didn't put a backslash \, at the end of the continued configure lines of switches, but that didn't seem to matter. I am not motivated to put much effort into troubleshooting as I wanted to look at Pre5 now, but the final release is due soon. Thanks for your advice, Stephen
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: lyx-users@lists.lyx.org Sent: Friday, February 17, 2006 1:45 PM Subject: Re: LyX on Cygwin Stephen Harris [EMAIL PROTECTED] writes: The Pre5 doesn't have a configure file to execute the several ./configure switches in Enrico's Howto. Are you sure? The lyx-1.4.0pre5.tar.bz2 archive I downloaded from ftp://ftp.devel.lyx.org/pub/lyx/pre/ had one ... Yes, I am sure that in both lyx-1.4.0pre5.tar.bz2 (or tar.gz) there is no configure file. Nor is there an autogen.sh file nor a configure.ac. All of those files are missing, the ones you would normally expect to see in lyx-devel. Just to be sure I have downloaded again ftp://ftp.devel.lyx.org/pub/lyx/pre/lyx-1.4.0pre5.tar.bz2 and those files are there... cd lyx-1.4.0pre5 ./autogen.sh I don't see how it is possible to run this command as the files are non-existent. The files can be found in the cvs lyx-devel directory, but your instructions don't say to use cvs for obtaining installation files which don't come as bz2 or tar.gz you say Unpack lyx-1.4.x.tar.bz2 in /usr/local/src (replace x ^ to match your archive name) But the files *are* there... Anyway, things do not change with a cvs version, simply replace lyx-1.4.x with lyx-devel ;-) I've already had the experience of not being able to compile the cvs files, but I was able to compile Lyx1.4.0pre3, so it is by no means certain that one can just adapt your configure switches to the current cvs files. Try it, it should work. Lyx1.4.0pre3 came with about 20 files not contained in Lyx1.4.0pre5. Since you say the files were contained The lyx-1.4.0pre5.tar.bz2 archive I downloaded ... had one it seems that somebody has deleted files from lyx-1.4.0pre5.tar.bz2 and tar.gz for that matter and repackaged. (no configure, configure.ac or autogen.sh plus many others) I think that nobody did that ;-) It may be a problem with the software you used to unpack the archive. Try using the cygwin tools: cd /usr/local/src tar jxvf /path/to/lyx-1.4.0pre5.tar.bz2 or tar zxvf /path/to/lyx-1.4.0pre5.tar.gz if you downloaded the .gz version. The problem I reported remains just as murky, Don't be desperate, try again. I am sure it is not so difficult. Did you succeeded in compiling Qt? -- Enrico I unpacked the archives with WinRar which is supposed to work but apparently didn't because using tar worked to display the files. I did not succeed in compiling Qt. I got the files in the right directory with cvs, but the ./configure failed quickly with the error make: *** [project.o] Error 1 qmake failed to build. Aborting Is this line correctly typed? ./configure -platform cygwin-g++-win32 -v -release -static also I didn't put a backslash \, at the end of the continued configure lines of switches, but that didn't seem to matter. I am not motivated to put much effort into troubleshooting as I wanted to look at Pre5 now, but the final release is due soon. Thanks for your advice, Stephen
Re: LyX on Cygwin
- Original Message - From: "Enrico Forestieri" <[EMAIL PROTECTED]> To: <lyx-users@lists.lyx.org> Sent: Friday, February 17, 2006 1:45 PM Subject: Re: LyX on Cygwin Stephen Harris <[EMAIL PROTECTED]> writes: >> The Pre5 doesn't have a configure file to execute >> the several ./configure switches in Enrico's Howto. > > Are you sure? The lyx-1.4.0pre5.tar.bz2 archive I downloaded from > ftp://ftp.devel.lyx.org/pub/lyx/pre/ had one ... > Yes, I am sure that in both lyx-1.4.0pre5.tar.bz2 (or tar.gz) there is no configure file. Nor is there an autogen.sh file nor a configure.ac. All of those files are missing, the ones you would normally expect to see in lyx-devel. Just to be sure I have downloaded again ftp://ftp.devel.lyx.org/pub/lyx/pre/lyx-1.4.0pre5.tar.bz2 and those files are there... > cd lyx-1.4.0pre5 > ./autogen.sh I don't see how it is possible to run this command as the files are non-existent. The files can be found in the cvs lyx-devel directory, but your instructions don't say to use cvs for obtaining installation files which don't come as bz2 or tar.gz you say "Unpack lyx-1.4.x.tar.bz2 in /usr/local/src >> >(replace x ^ to match your archive name)" But the files *are* there... Anyway, things do not change with a cvs version, simply replace "lyx-1.4.x" with "lyx-devel" ;-) I've already had the experience of not being able to compile the cvs files, but I was able to compile Lyx1.4.0pre3, so it is by no means certain that one can just adapt your configure switches to the current cvs files. Try it, it should work. Lyx1.4.0pre3 came with about 20 files not contained in Lyx1.4.0pre5. Since you say the files were contained "The lyx-1.4.0pre5.tar.bz2 archive I downloaded ... had one" it seems that somebody has deleted files from lyx-1.4.0pre5.tar.bz2 and tar.gz for that matter and repackaged. (no configure, configure.ac or autogen.sh plus many others) I think that nobody did that ;-) It may be a problem with the software you used to unpack the archive. Try using the cygwin tools: cd /usr/local/src tar jxvf /path/to/lyx-1.4.0pre5.tar.bz2 or tar zxvf /path/to/lyx-1.4.0pre5.tar.gz if you downloaded the .gz version. The problem I reported remains just as murky, Don't be desperate, try again. I am sure it is not so difficult. Did you succeeded in compiling Qt? -- Enrico I unpacked the archives with WinRar which is supposed to work but apparently didn't because using tar worked to display the files. I did not succeed in compiling Qt. I got the files in the right directory with cvs, but the ./configure failed quickly with the error make: *** [project.o] Error 1 qmake failed to build. Aborting Is this line correctly typed? ./configure -platform cygwin-g++-win32 -v -release -static also I didn't put a backslash \, at the end of the continued configure lines of switches, but that didn't seem to matter. I am not motivated to put much effort into troubleshooting as I wanted to look at Pre5 now, but the final release is due soon. Thanks for your advice, Stephen
LyX on Cygwin
http://wiki.lyx.org/LyX/LyXOnCygwin Unpack lyx-1.4.x.tar.bz2 in /usr/local/src (replace x ^ to match your archive name) I was reading over Enrico's detailed instructions. I can't find a lyx 1.4.0.tar.bz2 or tar.gz for download. The Pre5 doesn't have a configure file to execute the several ./configure switches in Enrico's Howto. The Pre3 release had a configure file but that isn't worthwhile trying to build. I downloaded the current cvs and didn't find a configure file. I was wary of mixing Enricos' Cygwin instructions with the INSTALL notes. And the cvs option is not offered in the Howto. The only download folder I found for lyx-1.4.x was ftp://ftp.devel.lyx.org/pub/lyx/pre/ Regards, Stephen
Re: LyX on Cygwin
Stephen Harris [EMAIL PROTECTED] writes: http://wiki.lyx.org/LyX/LyXOnCygwin Unpack lyx-1.4.x.tar.bz2 in /usr/local/src (replace x ^ to match your archive name) I was reading over Enrico's detailed instructions. I can't find a lyx 1.4.0.tar.bz2 or tar.gz for download. Well, x could also mean 0pre5 ;-) The Pre5 doesn't have a configure file to execute the several ./configure switches in Enrico's Howto. Are you sure? The lyx-1.4.0pre5.tar.bz2 archive I downloaded from ftp://ftp.devel.lyx.org/pub/lyx/pre/ had one ... The Pre3 release had a configure file but that isn't worthwhile trying to build. I downloaded the current cvs and didn't find a configure file. I was wary of mixing Enricos' Cygwin instructions with the INSTALL notes. And the cvs option is not offered in the Howto. The only download folder I found for lyx-1.4.x was ftp://ftp.devel.lyx.org/pub/lyx/pre/ As regards cvs, it's simply a matter of running ./autogen.sh. However, if you followed the directions, the script lyxconfig-cygwin should have informed you that configure was missing and should have also suggested what to do... run autogen.sh in the same directory containing configure.ac: cd lyx-1.4.0pre5 ./autogen.sh Please, tell me if something is not clear. -- Enrico
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: lyx-users@lists.lyx.org Sent: Friday, February 17, 2006 2:20 AM Subject: Re: LyX on Cygwin Stephen Harris [EMAIL PROTECTED] writes: http://wiki.lyx.org/LyX/LyXOnCygwin Unpack lyx-1.4.x.tar.bz2 in /usr/local/src (replace x ^ to match your archive name) I was reading over Enrico's detailed instructions. I can't find a lyx 1.4.0.tar.bz2 or tar.gz for download. Well, x could also mean 0pre5 ;-) The Pre5 doesn't have a configure file to execute the several ./configure switches in Enrico's Howto. Are you sure? The lyx-1.4.0pre5.tar.bz2 archive I downloaded from ftp://ftp.devel.lyx.org/pub/lyx/pre/ had one ... Yes, I am sure that in both lyx-1.4.0pre5.tar.bz2 (or tar.gz) there is no configure file. Nor is there an autogen.sh file nor a configure.ac. All of those files are missing, the ones you would normally expect to see in lyx-devel. I downloaded the current cvs and didn't find a configure file. I was wary of mixing Enricos' Cygwin instructions with the INSTALL notes. And the cvs option is not offered in the Howto. The only download folder I found for lyx-1.4.x was ftp://ftp.devel.lyx.org/pub/lyx/pre/ As regards cvs, it's simply a matter of running ./autogen.sh. However, if you followed the directions, the script lyxconfig-cygwin should have informed you that configure was missing and should have also suggested what to do... run autogen.sh in the same directory containing configure.ac: cd lyx-1.4.0pre5 ./autogen.sh Please, tell me if something is not clear. -- Enrico cd lyx-1.4.0pre5 ./autogen.sh I don't see how it is possible to run this command as the files are non-existent. The files can be found in the cvs lyx-devel directory, but your instructions don't say to use cvs for obtaining installation files which don't come as bz2 or tar.gz you say Unpack lyx-1.4.x.tar.bz2 in /usr/local/src (replace x ^ to match your archive name) I've already had the experience of not being able to compile the cvs files, but I was able to compile Lyx1.4.0pre3, so it is by no means certain that one can just adapt your configure switches to the current cvs files. Lyx1.4.0pre3 came with about 20 files not contained in Lyx1.4.0pre5. Since you say the files were contained The lyx-1.4.0pre5.tar.bz2 archive I downloaded ... had one it seems that somebody has deleted files from lyx-1.4.0pre5.tar.bz2 and tar.gz for that matter and repackaged. (no configure, configure.ac or autogen.sh plus many others) The problem I reported remains just as murky, Stephen
Re: LyX on Cygwin
Stephen Harris [EMAIL PROTECTED] writes: The Pre5 doesn't have a configure file to execute the several ./configure switches in Enrico's Howto. Are you sure? The lyx-1.4.0pre5.tar.bz2 archive I downloaded from ftp://ftp.devel.lyx.org/pub/lyx/pre/ had one ... Yes, I am sure that in both lyx-1.4.0pre5.tar.bz2 (or tar.gz) there is no configure file. Nor is there an autogen.sh file nor a configure.ac. All of those files are missing, the ones you would normally expect to see in lyx-devel. Just to be sure I have downloaded again ftp://ftp.devel.lyx.org/pub/lyx/pre/lyx-1.4.0pre5.tar.bz2 and those files are there... cd lyx-1.4.0pre5 ./autogen.sh I don't see how it is possible to run this command as the files are non-existent. The files can be found in the cvs lyx-devel directory, but your instructions don't say to use cvs for obtaining installation files which don't come as bz2 or tar.gz you say Unpack lyx-1.4.x.tar.bz2 in /usr/local/src (replace x ^ to match your archive name) But the files *are* there... Anyway, things do not change with a cvs version, simply replace lyx-1.4.x with lyx-devel ;-) I've already had the experience of not being able to compile the cvs files, but I was able to compile Lyx1.4.0pre3, so it is by no means certain that one can just adapt your configure switches to the current cvs files. Try it, it should work. Lyx1.4.0pre3 came with about 20 files not contained in Lyx1.4.0pre5. Since you say the files were contained The lyx-1.4.0pre5.tar.bz2 archive I downloaded ... had one it seems that somebody has deleted files from lyx-1.4.0pre5.tar.bz2 and tar.gz for that matter and repackaged. (no configure, configure.ac or autogen.sh plus many others) I think that nobody did that ;-) It may be a problem with the software you used to unpack the archive. Try using the cygwin tools: cd /usr/local/src tar jxvf /path/to/lyx-1.4.0pre5.tar.bz2 or tar zxvf /path/to/lyx-1.4.0pre5.tar.gz if you downloaded the .gz version. The problem I reported remains just as murky, Don't be desperate, try again. I am sure it is not so difficult. Did you succeeded in compiling Qt? -- Enrico
LyX on Cygwin
http://wiki.lyx.org/LyX/LyXOnCygwin Unpack lyx-1.4.x.tar.bz2 in /usr/local/src (replace x ^ to match your archive name) I was reading over Enrico's detailed instructions. I can't find a lyx 1.4.0.tar.bz2 or tar.gz for download. The Pre5 doesn't have a configure file to execute the several ./configure switches in Enrico's Howto. The Pre3 release had a configure file but that isn't worthwhile trying to build. I downloaded the current cvs and didn't find a configure file. I was wary of mixing Enricos' Cygwin instructions with the INSTALL notes. And the cvs option is not offered in the Howto. The only download folder I found for lyx-1.4.x was ftp://ftp.devel.lyx.org/pub/lyx/pre/ Regards, Stephen
Re: LyX on Cygwin
Stephen Harris [EMAIL PROTECTED] writes: http://wiki.lyx.org/LyX/LyXOnCygwin Unpack lyx-1.4.x.tar.bz2 in /usr/local/src (replace x ^ to match your archive name) I was reading over Enrico's detailed instructions. I can't find a lyx 1.4.0.tar.bz2 or tar.gz for download. Well, x could also mean 0pre5 ;-) The Pre5 doesn't have a configure file to execute the several ./configure switches in Enrico's Howto. Are you sure? The lyx-1.4.0pre5.tar.bz2 archive I downloaded from ftp://ftp.devel.lyx.org/pub/lyx/pre/ had one ... The Pre3 release had a configure file but that isn't worthwhile trying to build. I downloaded the current cvs and didn't find a configure file. I was wary of mixing Enricos' Cygwin instructions with the INSTALL notes. And the cvs option is not offered in the Howto. The only download folder I found for lyx-1.4.x was ftp://ftp.devel.lyx.org/pub/lyx/pre/ As regards cvs, it's simply a matter of running ./autogen.sh. However, if you followed the directions, the script lyxconfig-cygwin should have informed you that configure was missing and should have also suggested what to do... run autogen.sh in the same directory containing configure.ac: cd lyx-1.4.0pre5 ./autogen.sh Please, tell me if something is not clear. -- Enrico
Re: LyX on Cygwin
- Original Message - From: Enrico Forestieri [EMAIL PROTECTED] To: lyx-users@lists.lyx.org Sent: Friday, February 17, 2006 2:20 AM Subject: Re: LyX on Cygwin Stephen Harris [EMAIL PROTECTED] writes: http://wiki.lyx.org/LyX/LyXOnCygwin Unpack lyx-1.4.x.tar.bz2 in /usr/local/src (replace x ^ to match your archive name) I was reading over Enrico's detailed instructions. I can't find a lyx 1.4.0.tar.bz2 or tar.gz for download. Well, x could also mean 0pre5 ;-) The Pre5 doesn't have a configure file to execute the several ./configure switches in Enrico's Howto. Are you sure? The lyx-1.4.0pre5.tar.bz2 archive I downloaded from ftp://ftp.devel.lyx.org/pub/lyx/pre/ had one ... Yes, I am sure that in both lyx-1.4.0pre5.tar.bz2 (or tar.gz) there is no configure file. Nor is there an autogen.sh file nor a configure.ac. All of those files are missing, the ones you would normally expect to see in lyx-devel. I downloaded the current cvs and didn't find a configure file. I was wary of mixing Enricos' Cygwin instructions with the INSTALL notes. And the cvs option is not offered in the Howto. The only download folder I found for lyx-1.4.x was ftp://ftp.devel.lyx.org/pub/lyx/pre/ As regards cvs, it's simply a matter of running ./autogen.sh. However, if you followed the directions, the script lyxconfig-cygwin should have informed you that configure was missing and should have also suggested what to do... run autogen.sh in the same directory containing configure.ac: cd lyx-1.4.0pre5 ./autogen.sh Please, tell me if something is not clear. -- Enrico cd lyx-1.4.0pre5 ./autogen.sh I don't see how it is possible to run this command as the files are non-existent. The files can be found in the cvs lyx-devel directory, but your instructions don't say to use cvs for obtaining installation files which don't come as bz2 or tar.gz you say Unpack lyx-1.4.x.tar.bz2 in /usr/local/src (replace x ^ to match your archive name) I've already had the experience of not being able to compile the cvs files, but I was able to compile Lyx1.4.0pre3, so it is by no means certain that one can just adapt your configure switches to the current cvs files. Lyx1.4.0pre3 came with about 20 files not contained in Lyx1.4.0pre5. Since you say the files were contained The lyx-1.4.0pre5.tar.bz2 archive I downloaded ... had one it seems that somebody has deleted files from lyx-1.4.0pre5.tar.bz2 and tar.gz for that matter and repackaged. (no configure, configure.ac or autogen.sh plus many others) The problem I reported remains just as murky, Stephen
