Date: Fri, 02 Sep 2005 23:58:19 +0100 From: Alex Zbyslaw <xfb52@dial.pipex.com> To: Rein Kadastik <wigry@uninet.ee> Cc: freebsd-questions@freebsd.org Subject: Re: sed not working Message-ID: <4318D90B.5030807@dial.pipex.com> In-Reply-To: <4318B66E.3010603@uninet.ee> References: <4318B54B.6080001@uninet.ee> <4318B66E.3010603@uninet.ee>
next in thread | previous in thread | raw e-mail | index | archive | help
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 :-) --Alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4318D90B.5030807>