Re: Re[3]: lyx configure script

2002-07-15 Thread Jean-Marc Lasgouttes
> "Soeren" == Soeren Pietsch <[EMAIL PROTECTED]> writes: Soeren> This time with the patch ;) Soeren Excellent. I applied it to trunk and 1.2.x branch JMarc

Re[3]: lyx configure script

2002-07-11 Thread Soeren Pietsch
This time with the patch ;) Soeren Kayvan>> On Thu, Jul 11, 2002 at 08:01:25PM +0200, Soeren Pietsch wrote: >>> Kayvan>> It seems fine, except that I am concerned about checking for the exact >>> Kayvan>> string CYGWIN_NT-5.0 >>> >>> Kayvan>> What happens with the ``uname -s'' string changes to

Re[2]: lyx configure script

2002-07-11 Thread Soeren Pietsch
Kayvan> On Thu, Jul 11, 2002 at 08:01:25PM +0200, Soeren Pietsch wrote: >> Kayvan>> It seems fine, except that I am concerned about checking for the exact >> Kayvan>> string CYGWIN_NT-5.0 >> >> Kayvan>> What happens with the ``uname -s'' string changes to CYGWIN_NT-5.1? >> >> Kayvan>> I think it

Re: lyx configure script

2002-07-11 Thread Kayvan A. Sylvan
On Thu, Jul 11, 2002 at 08:01:25PM +0200, Soeren Pietsch wrote: > Kayvan>> It seems fine, except that I am concerned about checking for the exact > Kayvan>> string CYGWIN_NT-5.0 > > Kayvan>> What happens with the ``uname -s'' string changes to CYGWIN_NT-5.1? > > Kayvan>> I think it might be bett

Re[3]: lyx configure script

2002-07-11 Thread Soeren Pietsch
Kayvan>> It seems fine, except that I am concerned about checking for the exact Kayvan>> string CYGWIN_NT-5.0 Kayvan>> What happens with the ``uname -s'' string changes to CYGWIN_NT-5.1? Kayvan>> I think it might be better to have a case statement there: Kayvan>> sysname=`uname -s` Kayvan>> cas

Re[2]: lyx configure script

2002-07-09 Thread Soeren Pietsch
Kayvan> It seems fine, except that I am concerned about checking for the exact Kayvan> string CYGWIN_NT-5.0 Kayvan> What happens with the ``uname -s'' string changes to CYGWIN_NT-5.1? Kayvan> I think it might be better to have a case statement there: Kayvan> sysname=`uname -s` Kayvan> case "$sy

Re: lyx configure script

2002-07-09 Thread Kayvan A. Sylvan
It seems fine, except that I am concerned about checking for the exact string CYGWIN_NT-5.0 What happens with the ``uname -s'' string changes to CYGWIN_NT-5.1? I think it might be better to have a case statement there: sysname=`uname -s` case "$sysname" in CYGWIN*) [... code ...] ;; *)

Re[4]: lyx configure script

2002-07-09 Thread Soeren Pietsch
Kayvan> On Tue, Jul 09, 2002 at 05:21:07PM +0200, Jean-Marc Lasgouttes wrote: >> >>>>> "Soeren" == Soeren Pietsch <[EMAIL PROTECTED]> writes: >> >> >>>>>>> "Soeren" == Soeren Pietsch <[EMAIL PROTECTED]> writ

Re: Re[2]: lyx configure script

2002-07-09 Thread Kayvan A. Sylvan
On Tue, Jul 09, 2002 at 05:21:07PM +0200, Jean-Marc Lasgouttes wrote: > >>>>> "Soeren" == Soeren Pietsch <[EMAIL PROTECTED]> writes: > > >>>>>>> "Soeren" == Soeren Pietsch <[EMAIL PROTECTED]> writes: > Soeren&g

Re: Re[2]: lyx configure script

2002-07-09 Thread Jean-Marc Lasgouttes
>>>>> "Soeren" == Soeren Pietsch <[EMAIL PROTECTED]> writes: >>>>>>> "Soeren" == Soeren Pietsch <[EMAIL PROTECTED]> writes: Soeren> Hi, I had a bit of a problem with the lyx configure script on Soeren> a cygwin environ

Re[2]: lyx configure script

2002-07-09 Thread Soeren Pietsch
>>>>>> "Soeren" == Soeren Pietsch <[EMAIL PROTECTED]> writes: Soeren>> Hi, I had a bit of a problem with the lyx configure script on Soeren>> a cygwin environment. The following check only works if the sh Soeren>> shell points to the bash sh

Re: lyx configure script

2002-07-09 Thread Jean-Marc Lasgouttes
>>>>> "Soeren" == Soeren Pietsch <[EMAIL PROTECTED]> writes: Soeren> Hi, I had a bit of a problem with the lyx configure script on Soeren> a cygwin environment. The following check only works if the sh Soeren> shell points to the bash shell. Soeren> ##

lyx configure script

2002-06-24 Thread Soeren Pietsch
Hi, I had a bit of a problem with the lyx configure script on a cygwin environment. The following check only works if the sh shell points to the bash shell. ### Adjust PATH for Win32 (Cygwin) if test "x$OSTYPE" = xcygwin; then echo "configure: cygwin detected; path corre

Re: anomalities with detection of XForms and LyX-configure-script

2002-04-06 Thread Lars Gullik Bjønnes
"R. Lahaye" <[EMAIL PROTECTED]> writes: | Lars Gullik Bjønnes wrote: > >> Permission problem? > | Hmm, what could that be? This is what I use: > | 9352 -rwxr-xr-x 1 root wheel 9568172 Apr 6 17:27 libforms.a | 0 lrwxr-xr-x 1 root wheel 13 Apr 6 17:27 libforms.so -> | libforms.so.

Re: anomalities with detection of XForms and LyX-configure-script

2002-04-06 Thread R. Lahaye
Lars Gullik Bjønnes wrote: > Permission problem? Hmm, what could that be? This is what I use: 9352 -rwxr-xr-x 1 root wheel 9568172 Apr 6 17:27 libforms.a 0 lrwxr-xr-x 1 root wheel 13 Apr 6 17:27 libforms.so -> libforms.so.0 2176 -rwxr-xr-x 1 root wheel 2215018 Apr 6 17:27

Re: anomalities with detection of XForms and LyX-configure-script

2002-04-06 Thread Lars Gullik Bjønnes
"R. Lahaye" <[EMAIL PROTECTED]> writes: | Hi, > | I'm trying desperately to get LyX running with the recently opensourced | Xforms. Haven't succeeded yet, but found a few irregular behaviours with | the LyX configure script. > | When I install XForms, I get (by d

anomalities with detection of XForms and LyX-configure-script

2002-04-06 Thread R. Lahaye
Hi, I'm trying desperately to get LyX running with the recently opensourced Xforms. Haven't succeeded yet, but found a few irregular behaviours with the LyX configure script. When I install XForms, I get (by default): include/X11/forms.h lib/libforms.a lib/libforms.so -> libf