From owner-freebsd-current Sun Apr 21 9:43:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from espresso.q9media.com (espresso.q9media.com [216.254.138.122]) by hub.freebsd.org (Postfix) with ESMTP id E5A1537B405; Sun, 21 Apr 2002 09:43:45 -0700 (PDT) Received: (from mike@localhost) by espresso.q9media.com (8.11.6/8.11.6) id g3LGhLG01208; Sun, 21 Apr 2002 12:43:21 -0400 (EDT) (envelope-from mike) Date: Sun, 21 Apr 2002 12:43:21 -0400 From: Mike Barcroft To: John Hay Cc: freebsd-current@freebsd.org, wollman@freebsd.org Subject: Re: new expr(1) behaviour breaks libtool Message-ID: <20020421124321.T29857@espresso.q9media.com> References: <200204211558.g3LFwM414296@zibbi.icomtek.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200204211558.g3LFwM414296@zibbi.icomtek.csir.co.za>; from jhay@icomtek.csir.co.za on Sun, Apr 21, 2002 at 05:58:22PM +0200 Organization: The FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Hay 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 without it. :-((( I'm almost positive this issue was discussed before. Check the follow ups to the commit. > The place where I noticed it was when libtool started to complain > when compiling jade. Libtool does things like: > > expr -L/export/ports/textproc/jade/work/jade-1.2.1/lib/.libs : -l\(.*\) > expr -lsp : -l\(.*\) > expr -lm : -l\(.*\) > expr -lgrove : -l\(.*\) > > On -current this now have to be: > > expr -- -L/export/ports/textproc/jade/work/jade-1.2.1/lib/.libs : -l\(.*\) > expr -- -lsp : -l\(.*\) > expr -- -lm : -l\(.*\) > expr -- -lgrove : -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. :-((( This should exactly match the behavior of any certified UNIX system. > Yes, I did read the commit message, but I still think the behaviour > of the new expr(1) is wrong. Not according to the Standard, or the response from Garrett's request for clarification of the Standard. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message