new expr(1) behaviour breaks libtool

2002-04-21 Thread John Hay
Hi, I see the new new behaviour of expr(1) requires you to add '--' if your commandline arguments might start with a '-'. This does break things a little because our old expr(1) does not understand a '--' in the beginning and the new one don't work right without it. :-((( The place where I notic

Re: new expr(1) behaviour breaks libtool

2002-04-21 Thread Mike Barcroft
John Hay <[EMAIL PROTECTED]> writes: > I see the new new behaviour of expr(1) requires you to add '--' if your > commandline arguments might start with a '-'. This does break things > a little because our old expr(1) does not understand a '--' in the > beginning and the new one don't work right wi

Re: new expr(1) behaviour breaks libtool

2002-04-21 Thread John Hay
> > I see the new new behaviour of expr(1) requires you to add '--' if your > > commandline arguments might start with a '-'. This does break things > > a little because our old expr(1) does not understand a '--' in the > > beginning and the new one don't work right without it. :-((( > > I'm almo

Re: new expr(1) behaviour breaks libtool

2002-04-21 Thread Kris Kennaway
On Sun, Apr 21, 2002 at 05:58:22PM +0200, John Hay wrote: > Hi, > > I see the new new behaviour of expr(1) requires you to add '--' if your > commandline arguments might start with a '-'. This does break things > a little because our old expr(1) does not understand a '--' in the > beginning and t

Re: new expr(1) behaviour breaks libtool

2002-04-22 Thread Terry Lambert
John Hay wrote: > > > I see the new new behaviour of expr(1) requires you to add '--' if your > > > commandline arguments might start with a '-'. This does break things > > > a little because our old expr(1) does not understand a '--' in the > > > beginning and the new one don't work right without

Re: new expr(1) behaviour breaks libtool

2002-04-22 Thread Garrett Wollman
< said: >> > expr -lgrove : -l\(.*\) >> > expr -- -L/export/ports/textproc/jade/work/jade-1.2.1/lib/.libs : -l\(.*\) >> > If we are going to leave this behaviour, we will have to teach libtool >> > how to call expr(1) differently on -stable and -current and it looks >> > like yet again different

Re: new expr(1) behaviour breaks libtool

2002-04-24 Thread John Hay
> > I have just committed code to expr which will cause it to behave more > like the old expr did in the presence of an EXPR_COMPAT environment > variable. Ports can then be set up to build with this variable > defined until the libtool maintainers fix up their act. Thanks, with this and some p