Date: Sat, 03 Sep 2005 10:46:46 +0300 From: Rein Kadastik <wigry@uninet.ee> To: freebsd-questions@freebsd.org Subject: Re: sed not working Message-ID: <431954E6.1060802@uninet.ee> In-Reply-To: <4318D90B.5030807@dial.pipex.com> References: <4318B54B.6080001@uninet.ee> <4318B66E.3010603@uninet.ee> <4318D90B.5030807@dial.pipex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Alex Zbyslaw wrote:
> Rein Kadastik wrote:
>
>>
>> Rein Kadastik wrote:
>>
>>> Hi
>>>
>>> I have a problem with sed on one of my systems.
>>>
>>> Lets take the following command:
>>>
>>> sed -e '/^\([a-z_][a-z_]*\) /s//\1 gen_/'
>>>
>>> On all other systems the input would be transformed:
>>> int something() -> int gen_something()
>>>
>>> On the broken system, the transformation is not done:
>>> int something() -> int something()
>>>
>>> The broken system used to be 4.6-STABLE but I managed to upgrade it
>>> to 4.11-RELEASE-p11, hoping that the update procedure will fix the
>>> sed, but apparently not. Imagine the make buildworld without working
>>> sed :) Anyway I generated the files on other working system so I
>>> managed to get through the buildworld part. Installkernel and
>>> installworld did not used sed so no problems there.
>>>
>>> Does anybody have some ideas, what would be the reason? I tested the
>>> sed command also on 4.8-RELEASE and 4.10-STABLE where it works
>>> nicely. Even copied the sed over from working systems but no luck.
>>
>>
> You've probably tried this, but what does "which sed" show on the
> broken system? It should show /usr/bin/sed and if it doesn't, there's
> your problem :-)
It shows /usr/bin/sed
Ident shows the following:
# ident /usr/bin/sed
/usr/bin/sed:
$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.11 2004/01/10 06:30:37
tjr Exp $
The ident output is identical on the working system. I guess, that it is
some sort of a regex library issue, as sed itself does not contain regex
engine.
-- Rein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?431954E6.1060802>