---------- Forwarded message ----------
From: stefano franchi <stefano.fran...@gmail.com>
Date: Wed, Nov 13, 2013 at 9:46 AM
Subject: Re: Configure errors on Archlinux for lyx 2.1Beta
To: Kornel Benko <kor...@lyx.org>
On Wed, Nov 13, 2013 at 9:23 AM, Kornel Benko <kor...@lyx.org> wrote:
> Am Mittwoch, 13. November 2013 um 09:06:19, schrieb stefano franchi <
> stefano.fran...@gmail.com>
> > On Wed, Nov 13, 2013 at 8:40 AM, Kornel Benko <kor...@lyx.org> wrote:
> >
> > > Am Mittwoch, 13. November 2013 um 08:31:49, schrieb stefano franchi <
> > > stefano.fran...@gmail.com>
> > > > On Tue, Nov 12, 2013 at 9:54 AM, stefano franchi
> > > > <stefano.fran...@gmail.com>wrote:
> > > >
> > > > > Configuration of the recently released 2.1.beta on my Archlinux
> system
> > > > > gives python-related errors (see below).
> > > > >
> > > > > It looks like a python2 /python3 issue. On Archlinux, python
> defaults
> > > to
> > > > > python3, while the executable for python 2.7 is /usr/bin/python2
> > > > >
> > > > > Interestingly, configure itself ends successfully. My first
> attempt at
> > > > > compiling (i.e. make) failed immediately with a different
> > > python-related
> > > > > error. I tried again (without reconfiguring) and it worked.
> > > > >
> > > > > However, I do get the same error in the console when starting lyx.
> Lyx
> > > > > starts anyways, so I am not sure how serious this problem is.
> > > > >
> > > >
> > > >
> > > >
> > > > After a bit more testing, my guess is that the problem is most
> likely
> > > > with the (presumably) python script(s) that locate the existing
> LaTex
> > > > installation and configures LyX accordingly. That's what fails,
> thereby
> > > > making Lyx basically unusable.
> > > >
> > > > Could anyone tell me which scripts are responsible for LaTeX
> > > configuration?
> > > > I looked at a promising /lib/scripts/TeXFiles.py, but that one does
> not
> > > > seem to be the root of the problem.
> > >
> > > What about ./lib/configure.py?
> > >
> > >
> > Hmm, I missed that. Will look into it.
> >
> >
> > > > Any ideas?
> > > >
> > >
> > > Have you tried the cmake build?
> > >
> > >
> > I did. same problem (in fact I found out more about the issue by looking
> at
> > the results of the cmake build. Autoconf was absolutely cryptic to me).
> >
>
> I would try to patch ./src/support/os.cpp:103 (Dont know the globbing
> syntax here, (sh?))
> QStringList list = qdir.entryList(QStringList("python?"));
>
>
Problem solved. It was actually a local issue with my linux installation
and not a Lyx problem at all.
The os.cpp source you pointed me to does the correct thing and looks for a
python2 executable.
Here is what, apparently, threw it off course:
I had a link in my local ~/bin
~/bin/python --> /usr/bin/python2
and ~/bin comes before /usr/bin in my PATH
I cannot remember exactly why I had this link in place, I think it was a
hack that allowed me to overcome lyx-related problems in a previous
version.
At any rate, removing the links apparently allowed os.cpp to do its job and
solved the problem.
Thanks for pointing me in the right direction!
Cheers,
Stefano
--
__________________________________________________
Stefano Franchi
Associate Research Professor
Department of Hispanic Studies Ph: +1 (979) 845-2125
Texas A&M University Fax: +1 (979) 845-6421
College Station, Texas, USA
stef...@tamu.edu
http://stefano.cleinias.org
--
__________________________________________________
Stefano Franchi
Associate Research Professor
Department of Hispanic Studies Ph: +1 (979) 845-2125
Texas A&M University Fax: +1 (979) 845-6421
College Station, Texas, USA
stef...@tamu.edu
http://stefano.cleinias.org
