Why doesn't autoconf like our /bin/sh?
mwm at mired.org
Wed May 21 18:39:01 UTC 2008
On Fri, 16 May 2008 16:13:07 +0200 Stefan Farfeleder <stefan at fafoe.narf.at> wrote:
> On Fri, May 16, 2008 at 10:11:43AM -0400, Mike Meyer wrote:
> > On Fri, 16 May 2008 09:44:33 +0200
> > Stefan Farfeleder <stefan at fafoe.narf.at> wrote:
> > > On Sun, Mar 09, 2008 at 03:27:12PM -0400, Mike Meyer wrote:
> > > > I've stumbled on to an obscure problem with autoconf 2.61, and I'm not
> > > > sure quite what to do with it. I've already sent mail to the autoconf
> > > > folks, but I'd like to understand what's going on.
> > > >
> > > > The problem is that, on a FreeBSD system with only /bin/sh and the
> > > > ports zsh as installed shells, if you have SHELL set to zsh when
> > > > invoking the autoconf-generated configure script, the script produces
> > > > a broken Makefile. It doesn't generate an error, it just complains
> > > > that:
> > >
> > > Can you please retry? /bin/sh now supports expanding $LINENO which was
> > > often the reason for configure not liking it.
And autoconf seems happy to use it.
More information about the freebsd-hackers