Date: Sat, 3 Sep 2005 20:18:01 +1000 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: Rein Kadastik <wigry@uninet.ee> Cc: freebsd-hackers@freebsd.org Subject: Re: sed not working Message-ID: <20050903101800.GA77285@cirb503493.alcatel.com.au> In-Reply-To: <43196C96.6040504@uninet.ee> References: <43196C96.6040504@uninet.ee>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2005-Sep-03 12:27:50 +0300, Rein Kadastik wrote: >Lets take the following sed command (from the ncurses MKlib_gen.sh script): > >sed -e '/^\([a-z_][a-z_]*\) /s//\1 gen_/' ... >This works, but I have found a specific pattern, where it does not work: >int something -> int something >Does anybody have any idea, what would be the cause of the problem and >how to fix it. I can't reproduce it on 4.9 or 7. I presume you've double checked that your test input doesn't have any garbage characters in it (or a tab instead of a space). >I also have several other FreeBSD systems, where the sed behaves >correctly. I also copied the sed over to the broken system, but no luck. ... >I suspect, that it is some sort of a regex library issue as sed does not >contain its own regex engine. What happens if you copy the libc from the broken system to a working system? Is there anything unusual about the problematic system? -- Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050903101800.GA77285>