Date: Sun, 25 May 2008 09:06:47 -0600 From: John E Hein <jhein@timing.com> To: Stefan Farfeleder <stefan@fafoe.narf.at> Cc: hackers@freebsd.org, Mike Meyer <mwm@mired.org> Subject: Re: Why doesn't autoconf like our /bin/sh? Message-ID: <18489.32903.477434.465037@gromit.timing.com> In-Reply-To: <20080516141307.GB1032@lizard.fafoe.narf.at> References: <20080309152712.42752293@bhuda.mired.org> <20080516074433.GA1032@lizard.fafoe.narf.at> <20080516101143.3545937c@bhuda.mired.org> <20080516141307.GB1032@lizard.fafoe.narf.at>
next in thread | previous in thread | raw e-mail | index | archive | help
Stefan Farfeleder wrote at 16:13 +0200 on May 16, 2008:
> 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@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.
> >
> > Which branch, and how recently?
>
> HEAD and yesterday.
FWIW, it seems bash and sh report line number differently.
# grep -n ^ ~/tmp/ln
1:#!/bin/sh
2:echo f line: $LINENO
3:f()
4:{
5:echo f line: $LINENO
6:}
7:
8:f
9:echo main line: $LINENO
10:f
# /bin/sh ~/tmp/ln
f line: 2
f line: 3
main line: 9
f line: 3
# bash ~/tmp/ln
f line: 2
f line: 5
main line: 9
f line: 5
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18489.32903.477434.465037>