-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Pádraig Brady on 5/27/2009 10:20 AM:
> Take 2 attached.
>
> Still outstanding from the gnulib portion is support for solaris.
> I may get time to set this up, but I've very little time lately,
> so I would like not to require this for mer
Take 2 attached.
Still outstanding from the gnulib portion is support for solaris.
I may get time to set this up, but I've very little time lately,
so I would like not to require this for merging.
Also I didn't yet implement the optimization to coreutils
that Paul mentioned, to cache whether the
> While we already determined that the expression is using the non-portable
> \|, and thus using --posix is allowed to change the behavior, I think we
> have also found an actual bug in sed 4.2.
Not a bug, sed --posix disables \| altogether (and \+, \?, \<, \>,
etc.). Unless you had something dif
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Simon Josefsson on 5/27/2009 4:33 AM:
> j...@mocca:~/src/libidn master$ echo 'version 2 '|sed -e 's/version
> \(2\|2\.1\)\([ ,]\)/version 3\2/g'
> version 3
>
> But adding --posix makes it fail:
>
> j...@mocca:~/src/libidn master$ ec
Eric Blake writes:
> According to Simon Josefsson on 5/27/2009 4:33 AM:
>> But adding --posix makes it fail:
>>
>> j...@mocca:~/src/libidn master$ echo 'version 2 '|sed --posix -e 's/version
>> \(2\|2\.1\)\([ ,]\)/version 3\2/g'
>
> You are using \|, which is undefined in BRE, and therefore (c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Simon Josefsson on 5/27/2009 4:33 AM:
> But adding --posix makes it fail:
>
> j...@mocca:~/src/libidn master$ echo 'version 2 '|sed --posix -e 's/version
> \(2\|2\.1\)\([ ,]\)/version 3\2/g'
You are using \|, which is undefined in BRE,
I'm tracking down why gnulib-tool no longer updates license headers
correctly for me, and it boils down to me upgrading sed recently, and
that gnulib-tool invokes sed with --posix. This works:
j...@mocca:~/src/libidn master$ echo 'version 2 '|sed -e 's/version
\(2\|2\.1\)\([ ,]\)/version 3\2/g'
Mike Frysinger wrote:
> it's disabled explicitly because we dont want multibyte sucking up space on a
> system that doesnt need it.
You need to distinguish two things:
1) An implementation of ANSI C amendment 1 (MB_CUR_MAX, mbtowc, mblen,
mbstowcs,
wctomb, wcstombs, btowc, wctob, isw*, tow*
Mike Frysinger writes:
> there was never a situation of fix this *or* that. like i said earlier, the
> plan was to try and fix *all* relevant locations so that every possible
> package benefits. it's faster to start threads in parallel after all.
Maybe you can put '#define MB_CUR_MAX 1' in t
