Angus == Angus Leeming [EMAIL PROTECTED] writes:
I can do that too, but I cannot see cases where the test will
fail. Is -ne 100% portable?
Angus Shrug. That I cannot answer. It is in my O'Reilly book and
Angus works on both the linux and tru64 machines I have access to...
The autoconf info
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>> I can do that too, but I cannot see cases where the test will
>> fail. Is -ne 100% portable?
Angus> Shrug. That I cannot answer. It is in my O'Reilly book and
Angus> works on both the linux and tru64 machines I have access to...
The
Kayvan == Kayvan A Sylvan [EMAIL PROTECTED] writes:
Kayvan This is the end of the make install in making the lyx-1.3.x
Kayvan RPM:
Kayvan, could you check whether the problem is still there in
1.3.4cvs?
What happens is the following: if the makepsres program is available,
a PSres.upr
Jean-Marc Lasgouttes wrote:
Kayvan This is the end of the make install in making the
lyx-1.3.x Kayvan RPM:
Kayvan, could you check whether the problem is still there in
1.3.4cvs?
What happens is the following: if the makepsres program is
available, a PSres.upr (something that _may_ be
Angus Leeming [EMAIL PROTECTED] writes:
| However, I'm convinced that the configure file is wrong too. Why are
| you using '=' (a string test) when you should be using -eq (an
| integer test)?
| -if test ! $num = 0 ; then
| +if test $num -ne 0 ; then
does that matter?
I'd even use
if [
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus Ain't those '\' magic ;-)
Indeed...
Angus However, I'm convinced that the configure file is wrong too.
Angus Why are you using '=' (a string test) when you should be using
Angus -eq (an integer test)?
Angus -if test ! $num = 0 ; then +if
Jean-Marc Lasgouttes wrote:
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus Ain't those '\' magic ;-)
Indeed...
Angus However, I'm convinced that the configure file is wrong too.
Angus Why are you using '=' (a string test) when you should be
using Angus -eq (an integer test)?
> "Kayvan" == Kayvan A Sylvan <[EMAIL PROTECTED]> writes:
Kayvan> This is the end of the "make install" in making the lyx-1.3.x
Kayvan> RPM:
Kayvan, could you check whether the problem is still there in
1.3.4cvs?
What happens is the following: if the makepsres program is available,
a
Jean-Marc Lasgouttes wrote:
> Kayvan> This is the end of the "make install" in making the
> lyx-1.3.x Kayvan> RPM:
>
> Kayvan, could you check whether the problem is still there in
> 1.3.4cvs?
>
> What happens is the following: if the makepsres program is
> available, a PSres.upr (something
Angus Leeming <[EMAIL PROTECTED]> writes:
| However, I'm convinced that the configure file is wrong too. Why are
| you using '=' (a string test) when you should be using -eq (an
| integer test)?
>
| -if test ! $num = 0 ; then
| +if test $num -ne 0 ; then
does that matter?
I'd even use
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Ain't those '\' magic ;-)
Indeed...
Angus> However, I'm convinced that the configure file is wrong too.
Angus> Why are you using '=' (a string test) when you should be using
Angus> -eq (an integer test)?
Angus> -if test ! $num =
Jean-Marc Lasgouttes wrote:
>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> Ain't those '\' magic ;-)
>
> Indeed...
>
> Angus> However, I'm convinced that the configure file is wrong too.
> Angus> Why are you using '=' (a string test) when you should be
> using Angus>
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus test $num -ne 0 which makepsres /dev/null { ... (cd
Angus xfonts ; rm -f PSres.upr ; makepsres -q) || true
Angus }
Angus Finally, what's with the '|| true'?
The idea was to avoid an error if the program makepsres did not exist.
But it
Jean-Marc Lasgouttes wrote:
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus test $num -ne 0 which makepsres /dev/null { ... (cd
Angus xfonts ; rm -f PSres.upr ; makepsres -q) || true
Angus }
Angus Finally, what's with the '|| true'?
The idea was to avoid an error if the
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> test $num -ne 0 && which makepsres > /dev/null && { ... (cd
Angus> xfonts ; rm -f PSres.upr ; makepsres -q) || true
Angus> }
Angus> Finally, what's with the '|| true'?
The idea was to avoid an error if the program makepsres did
Jean-Marc Lasgouttes wrote:
>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> test $num -ne 0 && which makepsres > /dev/null && { ... (cd
> Angus> xfonts ; rm -f PSres.upr ; makepsres -q) || true
> Angus> }
>
> Angus> Finally, what's with the '|| true'?
>
> The idea was to
On Sunday 28 September 2003 10:02 pm, Kayvan A. Sylvan wrote:
That is somewhat off topic. I do intend to have the lyx-common,
lyx-xforms and lyx-qt RPMs being built, but that has nothing to do
with the current build failures.
Perhaps, but I didn't want anyone to forget that the work has been
Kayvan == Kayvan A Sylvan [EMAIL PROTECTED] writes:
Kayvan On Sun, Sep 28, 2003 at 09:58:50PM +, Angus Leeming wrote:
Kayvan A. Sylvan wrote:
Anyone have any suggestions for how to fix this here?
None, but I would like to remind you about Ling Li's 17 September
email Separate LyX
On Mon, Sep 29, 2003 at 10:29:08PM +0200, Jean-Marc Lasgouttes wrote:
Kayvan == Kayvan A Sylvan [EMAIL PROTECTED] writes:
Kayvan On Sun, Sep 28, 2003 at 09:58:50PM +, Angus Leeming wrote:
Kayvan A. Sylvan wrote:
Anyone have any suggestions for how to fix this here?
None, but
Kayvan A. Sylvan wrote:
This seems to be related to the execution of the makepsres command
that I added recently for solaris. Do you have a *.upr file created in
lib/xfonts?
No, I don't have the '*.upr' files created. I will investigate. Thanks
for the tip.
Perhaps the fix is similar to
Angus Leeming wrote:
test ! $num = 0 which makepsres /dev/null {
I missed this. Why are we testing if a string is equal is 0? Equality of
integers seems to be what is needed here
if test ! $num -eq 0; then
and why not
if test $num -ne 0; then
???
S
test $num -ne 0 which
On Sunday 28 September 2003 10:02 pm, Kayvan A. Sylvan wrote:
> That is somewhat off topic. I do intend to have the lyx-common,
> lyx-xforms and lyx-qt RPMs being built, but that has nothing to do
> with the current build failures.
Perhaps, but I didn't want anyone to forget that the work has
> "Kayvan" == Kayvan A Sylvan <[EMAIL PROTECTED]> writes:
Kayvan> On Sun, Sep 28, 2003 at 09:58:50PM +, Angus Leeming wrote:
>> Kayvan A. Sylvan wrote:
>>
>> > Anyone have any suggestions for how to fix this here?
>>
>> None, but I would like to remind you about Ling Li's 17 September
On Mon, Sep 29, 2003 at 10:29:08PM +0200, Jean-Marc Lasgouttes wrote:
> > "Kayvan" == Kayvan A Sylvan <[EMAIL PROTECTED]> writes:
>
> Kayvan> On Sun, Sep 28, 2003 at 09:58:50PM +, Angus Leeming wrote:
> >> Kayvan A. Sylvan wrote:
> >>
> >> > Anyone have any suggestions for how to fix
Kayvan A. Sylvan wrote:
>> This seems to be related to the execution of the makepsres command
>> that I added recently for solaris. Do you have a *.upr file created in
>> lib/xfonts?
>
> No, I don't have the '*.upr' files created. I will investigate. Thanks
> for the tip.
Perhaps the fix is
Angus Leeming wrote:
> test ! $num = 0 && which makepsres > /dev/null && {
I missed this. Why are we testing if a string is equal is 0? Equality of
integers seems to be what is needed here
if test ! $num -eq 0; then
and why not
if test $num -ne 0; then
???
S
test $num -ne 0 && which
Anyone have any suggestions for how to fix this here?
- Forwarded message from Kayvan A. Sylvan [EMAIL PROTECTED] -
Date: Fri, 26 Sep 2003 22:20:26 -0700
From: Kayvan A. Sylvan [EMAIL PROTECTED]
To: LyX Developers [EMAIL PROTECTED]
Subject: lyx-1.3.x compile failure
User-Agent: Mutt
Kayvan A. Sylvan wrote:
Anyone have any suggestions for how to fix this here?
None, but I would like to remind you about Ling Li's 17 September email
Separate LyX RPMs and lyx-select.sh
http://article.gmane.org/gmane.editors.lyx.devel:28064
We have decided in the past that this is exactly
On Sun, Sep 28, 2003 at 09:58:50PM +, Angus Leeming wrote:
Kayvan A. Sylvan wrote:
Anyone have any suggestions for how to fix this here?
None, but I would like to remind you about Ling Li's 17 September email
Separate LyX RPMs and lyx-select.sh
Anyone have any suggestions for how to fix this here?
- Forwarded message from "Kayvan A. Sylvan" <[EMAIL PROTECTED]> -
Date: Fri, 26 Sep 2003 22:20:26 -0700
From: "Kayvan A. Sylvan" <[EMAIL PROTECTED]>
To: LyX Developers <[EMAIL PROTECTED]>
Subject
Kayvan A. Sylvan wrote:
> Anyone have any suggestions for how to fix this here?
None, but I would like to remind you about Ling Li's 17 September email
"Separate LyX RPMs and lyx-select.sh"
http://article.gmane.org/gmane.editors.lyx.devel:28064
We have decided in the past that this is
On Sun, Sep 28, 2003 at 09:58:50PM +, Angus Leeming wrote:
> Kayvan A. Sylvan wrote:
>
> > Anyone have any suggestions for how to fix this here?
>
> None, but I would like to remind you about Ling Li's 17 September email
> "Separate LyX RPMs and lyx-select.sh"
>
>
This is the end of the make install in making the lyx-1.3.x RPM:
/usr/bin/install -c -m 644 xfonts/fonts.dir /var/tmp/lyx-1.3.4cvs-root/usr/share
/lyx/xfonts/fonts.dir ; \
/usr/bin/install -c -m 644 xfonts/fonts.scale /var/tmp/lyx-1.3.4cvs-root/usr/sha
re/lyx/xfonts/fonts.scale
mkdir
This is the end of the "make install" in making the lyx-1.3.x RPM:
/usr/bin/install -c -m 644 xfonts/fonts.dir /var/tmp/lyx-1.3.4cvs-root/usr/share
/lyx/xfonts/fonts.dir ; \
/usr/bin/install -c -m 644 xfonts/fonts.scale /var/tmp/lyx-1.3.4cvs-root/usr/sha
re/lyx/xfonts/fonts.scale
mkdir
34 matches
Mail list logo
