New expr(1) breaks ports
...for example, the w3m port. As part of the configure script, it executes the following shell command: expr --prefix=/usr/local : -*prefix=\(.*\) expr: syntax error Is expr to blame, or w3m? Kris msg36527/pgp0.pgp Description: PGP signature
New expr(1) breaks ports
On Sun, 24 Mar 2002 16:59:36 -0800, Kris Kennaway [EMAIL PROTECTED] said: expr --prefix=/usr/local : -*prefix=\(.*\) expr: syntax error Is expr to blame, or w3m? w3m is to blame. See expr(1) for more details and a workaround which is portable to both historic and POSIX expr implementations. (Allegedly, the new expr behavior is already required of all UNIX-branded systems, so the w3m authors should be well familiar with it. It is an old POSIX.2 requirement.) -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New expr(1) breaks ports
On Sun, Mar 24, 2002 at 08:05:26PM -0500, Garrett Wollman wrote: On Sun, 24 Mar 2002 16:59:36 -0800, Kris Kennaway [EMAIL PROTECTED] said: expr --prefix=/usr/local : -*prefix=\(.*\) expr: syntax error Is expr to blame, or w3m? w3m is to blame. See expr(1) for more details and a workaround which is portable to both historic and POSIX expr implementations. (Allegedly, the new expr behavior is already required of all UNIX-branded systems, so the w3m authors should be well familiar with it. It is an old POSIX.2 requirement.) OK. Looking at the latest build logs there are only about 13/3500 ports which are broken with this, so it's not too bad. Kris msg36529/pgp0.pgp Description: PGP signature
