From owner-freebsd-current Mon Oct 26 16:41:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15441 for freebsd-current-outgoing; Mon, 26 Oct 1998 16:41:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15431 for ; Mon, 26 Oct 1998 16:41:14 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id RAA19731; Mon, 26 Oct 1998 17:40:36 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd019684; Mon Oct 26 17:40:27 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id RAA29779; Mon, 26 Oct 1998 17:40:25 -0700 (MST) From: Terry Lambert Message-Id: <199810270040.RAA29779@usr07.primenet.com> Subject: Re: Shells for you and shells for me To: drosih@rpi.edu (Garance A Drosihn) Date: Tue, 27 Oct 1998 00:40:25 +0000 (GMT) Cc: chris@netmonger.net, current@FreeBSD.ORG In-Reply-To: from "Garance A Drosihn" at Oct 26, 98 04:07:00 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > To give a recent example I've stumbled across, a few 'autoconf'- > generated scripts will not work under freebsd, due to the way our > /bin/sh handles IFS processing. This is more than a someone wanting > tab completion or ~ expansion in /bin/sh, it's a practical issue when > porting software. Yes, recursive macro expansion does not work; that's either a "make" issue or a "sh" issue, depending on where you want to push the blame. > The problem with this particular example is that 'autoconf' is > probably wrong in what it's doing. Sure, it works on most > platforms, but various standards imply that it should not > work. Also, there is another way for it to do what it wants > to do, which is certain to work in all cases were it currently > works, as well as FreeBSD's '/bin/sh' and a few other shells. Exactly my opinion, actually. There is one autoconf generated makefile that assumes recursive macro expansion (in general, files generates by configure generated by autoconf are tending to require GNU make for the reason that ..uh...er... no good reason). In fact, there is one set of code, the Cyrus ACAPD code, that is known to not compile with the GNU toolchain, yet require GNU make after the configure. Bletch. Depending on features that result in undefined behaviour according to the relevent standards is Just Plain Wrong(tm). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message