Re: UGLY_DEFS for darwin in configure.in

[Thomas Treichl]

John W. Eaton schrieb:
> On  3-Oct-2007, Thomas Treichl wrote:
>
> | John W. Eaton schrieb:
> | > On  3-Oct-2007, Thomas Treichl wrote:
> | > 
> | > | My suggestion would be to reject because it really isn't a problem
> | > | to install a very new GNU's sed on any platform and use this beside
> | > | any other old sed that is installed
> | > 
> | > Does the following patch properly reject the default broken sed on
> | > your system?
> | > 
> | > jwe
> | 
> | No sorry, the output looks like Mac's sed is still usable:
> | 
> |    <SNIP>
> |    checking for times... yes
> |    checking for gawk... gawk
> |    checking for a usable sed... /usr/bin/sed
> |    checking for perl... perl
> |    checking for python... python
> |    <SNIP>
>
> Oops, the line
>
>   if test "`echo 'this and that' | sed -n 's/\(this\|that\).*$/\1/p'`" != 
> "this"; then
>
> should be
>
>   if test "`echo 'this and that' | ${_sed} -n 's/\(this\|that\).*$/\1/p'`" != 
> "this"; then
>
> jwe

This looks very good now. It automatically found my /usr/local/bin/sed as a 
working GNU's sed and didn't use /usr/bin/sed. Then I moved /usr/local/bin/sed 
into /usr/local/bin/__sed and my output now is:

  checking for times... yes
  checking for gawk... gawk
  checking for a usable sed...
  checking for perl... perl
  checking for python... python

One last question (because I used the ./configure SED=... command before and it 
didn't work then): The first line of the OCTAVE_PROG_SED macro is

  if test -z "$SED"; then

just for my understanding, we keep this line because the user in general should 
know better then the test script that he has a working SED program?

 Thanks for this long work,

  Thomas