Date: Mon, 22 Apr 2002 17:24:46 -0400 (EDT) From: Garrett Wollman <wollman@lcs.mit.edu> To: John Hay <jhay@icomtek.csir.co.za> Cc: freebsd-current@FreeBSD.ORG Subject: Re: new expr(1) behaviour breaks libtool Message-ID: <200204222124.g3MLOkJ03799@khavrinen.lcs.mit.edu> In-Reply-To: <200204211817.g3LIHTQ18310@zibbi.icomtek.csir.co.za> References: <20020421124321.T29857@espresso.q9media.com> <200204211817.g3LIHTQ18310@zibbi.icomtek.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Sun, 21 Apr 2002 20:17:29 +0200 (SAT), John Hay <jhay@icomtek.csir.co.za> 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 from the rest of the world. :-((( No, you just have to teach libtool to properly protect the arguments to expr(1). libtool 1.4 does this for some numeric operations, but not for string parsing. expr(1) goes into some detail about this, but the simple answer is: expr "X$arg" : 'X-l\(.*\)' is what's required. (There is nothing special about the character `X', other than it not being a hyphen.) 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. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200204222124.g3MLOkJ03799>