Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 09 Oct 2002 23:01:22 -0400
From:      Bill Moran <wmoran@potentialtech.com>
To:        "Simon 'corecode' Schubert" <corecode@corecode.ath.cx>
Cc:        Wayne M Barnes <stabilizer@klentaq.com>, freebsd-stable@freebsd.org
Subject:   Re: New sed breaks ports
Message-ID:  <3DA4ED82.50605@potentialtech.com>
References:  <20021009210042.A3027@klentaq.com>	<20021010040550.2539c6f2.corecode@corecode.ath.cx>	<20021009211658.A3071@klentaq.com> <20021010043359.33b0290d.corecode@corecode.ath.cx>

next in thread | previous in thread | raw e-mail | index | archive | help
I'm having problems getting OpenOffice to install, and I'm having
problems with no -i available, but it's not with sed, it's complaining
that XARGS doesn't have -i available.

Simon 'corecode' Schubert wrote:
> Obviously Wayne M Barnes formed the bits:
>>    I did a complete cvsup including the ports.
>>    I did a complete make world.
>>    I did a complete generic kernel install on the laptop.
> sounds good (if you did a make world or make installworld, not just make
> buildworld)

My system updates source/ports via cvsup nightly from a cronjob (actually,
the server does this and my system has that stuff mounted via NFS)
I did a complete [build|install][kernel|world] just two days ago.

>>    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.
> 
> because this is a known problem. 4.6.2 was the latest release that
> didn't include sed -i. -STABLE after that contains sed -i.

I did try to install OpenOffice while the system was still 4.5-SOMETHING
and it installed sed_inplace, then failed to complete the OpenOffice
build.  I did some research, saw the note to upgrade to the latest
before installing OpenOffice, and did the new world/kernel, then
tried OpenOffice again.  That's when I got the errors about not
having -i

> you could investigate that by checking idents:
> 
> freebsd4-6-2% ident `which sed`
> /usr/bin/sed:
>      $FreeBSD: src/usr.bin/sed/compile.c,v 1.13.2.4 2002/04/26 07:43:50 sobomax Exp $
>      $FreeBSD: src/usr.bin/sed/main.c,v 1.9.2.4 2001/11/29 05:22:44 mikeh Exp $
>      $FreeBSD: src/usr.bin/sed/misc.c,v 1.3.2.1 2001/11/29 05:22:44 mikeh Exp $
>      $FreeBSD: src/usr.bin/sed/process.c,v 1.10.2.4 2002/04/20 00:24:15 jmallett Exp $
> 
> a recent system should produce these versions:
> $FreeBSD: src/usr.bin/sed/compile.c,v 1.13.2.8 2002/08/17 05:47:06 tjr Exp $
> $FreeBSD: src/usr.bin/sed/main.c,v 1.9.2.7 2002/08/06 10:03:29 fanf Exp $
> $FreeBSD: src/usr.bin/sed/misc.c,v 1.3.2.2 2002/07/17 09:35:56 tjr Exp $
> $FreeBSD: src/usr.bin/sed/process.c,v 1.10.2.9 2002/08/17 05:47:06 tjr Exp $

These are the exact version numbers I'm getting.  But (unless I'm misinterpreting
the error messages) it's not sed that's the problem, it's xargs.

> if not, you screwed something on either cvsup,build or install

Possibly.  I'd like to know what I screwed, so I can unscrew it. ;)

-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com


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?3DA4ED82.50605>