octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: odepkg on Mac (was: Octave 4.2.0 release candidate 1 available for f


From: Mike Miller
Subject: Re: odepkg on Mac (was: Octave 4.2.0 release candidate 1 available for ftp)
Date: Fri, 9 Sep 2016 15:22:06 -0700
User-agent: NeoMutt/ (1.7.0)

On Fri, Sep 09, 2016 at 20:47:02 +0200, Sebastian wrote:
> > Am 09.09.2016 um 20:44 schrieb Carlo De Falco <address@hidden>:
> > 
> > 
> > On 9 Sep 2016, at 20:22, Carlo De Falco <address@hidden> wrote:
> > 
> >> 
> >> On 9 Sep 2016, at 20:15, Mike Miller <address@hidden> wrote:
> >> 
> >>> Is it another case of sed vs ${SED}?
> >> 
> >> I already suggested that...
> >> 
> >> @Sebastian, you say you checked, didn't you?
> >> What did you do exactly to check?
> > 
> > I tried the following :
> > 
> > - change any occurrence of 'sed' to ${SED} in 
> > build-aux/mk-octave-config-h.sh
> > - ln -s /usr/local/bin/gsed /usr/local/bin/sed 
> > - ./configure SED=/usr/local/bin/gsed
> > 
> > but still the macros to not appear in octave-config-h
> > 
> > c.
> 
> I checked on my machine, too. Configure reports "checking for a usable sed... 
> /usr/local/opt/gnu-sed/bin/gsed". So it should be correct? Any other idea?

That is not enough in this case. That confirms that the variable SED is
set to gsed, but what happens if a script doesn't use it and calls sed
directly?

Please try building from scratch with the attached patch.

-- 
mike

Attachment: oct-sed.patch
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]