Date: Thu, 10 Oct 2002 14:44:47 +0900 From: Yoshinori KASAZAKI <mia@gold.ocn.ne.jp> To: dsyphers@uchicago.edu Cc: freebsd-stable@freebsd.org Subject: Re: New sed breaks ports Message-ID: <20021010144447.090ec5c3.mia@gold.ocn.ne.jp> In-Reply-To: <200210092131.11605.dsyphers@uchicago.edu> References: <20021009210042.A3027@klentaq.com> <20021010040550.2539c6f2.corecode@corecode.ath.cx> <20021009211658.A3071@klentaq.com> <200210092131.11605.dsyphers@uchicago.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi.
On Wed, 9 Oct 2002 21:31:11 -0500
David Syphers <dsyphers@uchicago.edu> wrote:
> On Wednesday 09 October 2002 09:16 pm, Wayne M Barnes wrote:
> > Dear corecode,
> >
> > I did a complete cvsup including the ports.
> > I did a complete make world.
> > I did a complete generic kernel install on the laptop.
> >
> > Why are you mentioning 4.6.2? I only mentioned 4.7-RC (although
> > I am operating on memory here; it was RELENG_4 on Oct. 4 or 5.), and
> > 4.7-PRELEASE.
>
> He mentioned 4.6.2 because the MFC for sed to accept -i took place on June 26.
I'm using
> uname -a
FreeBSD intasity.akd.or.jp 4.7-RC FreeBSD 4.7-RC #25: Thu Oct 10 00:07:07 JST 2002 mia@intasity.akd.or.jp:/usr/obj/usr/src/sys/INTASITY i386
I get following ...
> sed -i
sed: option requires an argument -- i
usage: sed script [-Ean] [-i extension] [file ...]
sed [-an] [-i extension] [-e script] ... [-f script_file] ... [file ...]
> sed -i foo
sed: -i may not be used with stdin
If this is the case, it seems like sed is invoked without extension.
(I don't know why, though...)
mercenary
//
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021010144447.090ec5c3.mia>