From owner-freebsd-bugs Fri Apr 3 14:05:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13662 for freebsd-bugs-outgoing; Fri, 3 Apr 1998 14:05:57 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from sparky.franz.com (sparky.franz.com [192.132.95.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13640 for ; Fri, 3 Apr 1998 14:05:52 -0800 (PST) (envelope-from dancy@franz.com) Received: from ultra.franz.com by sparky.franz.com (8.8.8/FI-2.0) id OAA01981; Fri, 3 Apr 1998 14:05:49 -0800 (PST) Received: from ultra by ultra.franz.com (SMI-8.6/FI-2.0) id OAA14425; Fri, 3 Apr 1998 14:05:49 -0800 Message-Id: <199804032205.OAA14425@ultra.franz.com> To: Martin Cracauer cc: freebsd-bugs@hub.freebsd.org Subject: Re: bin/6047: /bin/sh does not handle -e option properly In-reply-to: Your message of "Sat, 04 Apr 1998 00:00:21 +0200." <19980404000021.01289@cons.org> Date: Fri, 03 Apr 1998 14:05:48 -0800 From: Ahmon Dancy Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> In <199804032100.NAA13627@ultra.franz.com>, Ahmon Dancy wrote: >> > >> Could you please test the appended fix? It fixes the particual >> > >> problem, the question is what else it br(e)ak(e)s :-) >> > >> >> > >> In case you don't want to build a shell, I put a binary with this fix >> > >> on >> > >> http://www.freebsd.org/~cracauer/sh.gz >> > >> > I tried this out and it seems to work, however it has been compiled >> > and linked w/ a newer shared library than the one I have on my >> > system. I tried extracting /usr/src/bin from the Feb 98 snapshot CD >> > but apparently the printf.c file is missing. Can you send me a >> > tarball of your /usr/src/bin/sh? >> >> My "sh" src doesn't contain printf, too, sh's Makefile has a relative >> path in it (to /usr/src/usr.bin/printf/). >> >> Anyway. just get >> ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/usr.bin/printf/print.c >> and copy it into your sh directory. Beautiful. I'll let you know how it goes. This is perfect timing because I'm about to work on the script that originally caused me to find this problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message