Re: sed broken

["Pouya D. Tafti" <pouya%san-serriffe.org@localhost>]

The issue seems to be related to libc:  I had an old pkg_comp chroot
jail lying around, and observed this:

    laptop$ echo 'foo*bar' | /var/chroot/pkg_comp/test/usr/bin/sed
's/*/-/g'
    -f-o-o-*-b-a-r-

BUT:

    laptop$ echo 'foo*bar' |
LD_LIBRARY_PATH=/var/chroot/pkg_comp/test/usr/lib
/var/chroot/pkg_comp/test/usr/bin/sed 's/*/-/g'
    foo-bar

The newly rebuilt libc still fails with both the old and the new sed:

    laptop$ echo 'foo*bar' | LD_LIBRARY_PATH=/usr/destdir/usr/lib
/var/chroot/pkg_comp/test/usr/bin/sed 's/*/-/g'
    -f-o-o-*-b-a-r-

    laptop$ echo 'foo*bar' | LD_LIBRARY_PATH=/usr/destdir/usr/lib
/usr/tooldir/bin/nbsed 's/*/-/g'
    -f-o-o-*-b-a-r-

Any suggestions what to try next?  Rebuilding the system afresh
doesn't seem to be helping much.

Pouya


On 11 February 2011 15:16, Paul Goyette <paul%whooppee.com@localhost> wrote:
> On amd64, with tools from just a short while ago, I get
>
> Â Â Â Â# echo 'foo*bar' | ./tools/x86_64/amd64/bin/nbsed -e 's/*/-/g'
> Â Â Â Âfoo-bar
> Â Â Â Â#
>
> On Fri, 11 Feb 2011, Pouya D. Tafti wrote:
>
>> On 11 February 2011 14:55, Martin Husemann <martin%duskware.de@localhost> 
>> wrote:
>>>
>>> On Fri, Feb 11, 2011 at 02:32:35PM +0100, Pouya D. Tafti wrote:
>>>>
>>>> Is anyone else seeing this? ÂShould I file a PR?
>>>
>>> I can't reproduce it with a -current updated ~two hours ago.
>>
>> Thank you.
>>
>> I just updated the sources, nuked /usr/objdir and /usr/tooldir, and
>> started a fresh build without -u. ÂStill, with the freshly rebuilt
>> /usr/tooldir/bin/nbsed I see:
>>
>> laptop$ echo 'foo*bar' | /usr/tooldir/bin/nbsed -e 's/*/-/g'
>> -f-o-o-*-b-a-r-
>>
>> I'm at a complete loss as to what to do next...
>>
>> Pouya