Why doesn't autoconf like our /bin/sh?

John E Hein jhein at timing.com
Sun May 25 16:09:20 UTC 2008


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 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.
 > > 
 > > 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



More information about the freebsd-hackers mailing list