KO Myung-Hun wrote:
> > PATH_SEPARATOR is the right approach, yes. In m4/progtest.m4 and
> > m4/lib-ld.m4
> > you find a code snippet that determines PATH_SEPARATOR. You can copy this to
> > init.sh.
> >
>
> Ok. Here is the patch.
Thanks. Looks perfect. Applied.
Bruno
I did this:
> 2017-09-26 Bruno Haible
>
> vma-iter: Improvements for Linux and BSD platforms.
> - Add support for DragonFly BSD.
> - Make it more reliable on Linux, GNU/kFreeBSD, FreeBSD, NetBSD.
> * lib/vma-iter.c (struct rofile, rof_open, rof_peekchar, rof_close):
>
Hi/2.
Bruno Haible wrote:
> Hi,
>
> KO Myung-Hun wrote:
>>> With your patch, does the following command sequence pass its tests?
>>>
>>> $ ./gnulib-tool --create-testdir --dir=testdir1 --single-configure
>>> --with-c++-tests wcwidth
>>> $ cd testdir1
>>> $ ./configure
>>> $ make
>>> $
I did this:
> 2017-10-01 Bruno Haible
>
> vma-iter: Add support for GNU/Hurd.
> * lib/vma-iter.c: Treat GNU/Hurd like Linux.
> * lib/vma-iter.h (VMA_ITERATE_SUPPORTED): Define also on GNU/kFreeBSD.
but this implementation does not show the VMAs from anonymous mmap. Sigh.
This
Bruno Haible wrote:
> KO Myung-Hun wrote:
>>> Does the init.sh test failure go away with this patch?
>>>
>>
>> 'shopt' related failure disappeared.
>
> OK, I've pushed the patch.
>
>> However, 'invalid path dir' is
>> still. I looked into that. And ':' was a problem. Because ':' is not a
>> pat
KO Myung-Hun wrote:
> > Does the init.sh test failure go away with this patch?
> >
>
> 'shopt' related failure disappeared.
OK, I've pushed the patch.
> However, 'invalid path dir' is
> still. I looked into that. And ':' was a problem. Because ':' is not a
> path separator on OS/2. Instead it's
Hi/2.
Bruno Haible wrote:
> KO Myung-Hun wrote:
>> I attach test-suite.log.
>
> Does the init.sh test failure go away with this patch?
>
'shopt' related failure disappeared. However, 'invalid path dir' is
still. I looked into that. And ':' was a problem. Because ':' is not a
path separator on O
Hi,
KO Myung-Hun wrote:
> > With your patch, does the following command sequence pass its tests?
> >
> > $ ./gnulib-tool --create-testdir --dir=testdir1 --single-configure
> > --with-c++-tests wcwidth
> > $ cd testdir1
> > $ ./configure
> > $ make
> > $ make check
> >
>
> I attach te
KO Myung-Hun wrote:
> I attach test-suite.log.
Does the init.sh test failure go away with this patch?
diff --git a/tests/init.sh b/tests/init.sh
index 470605c..0821c57 100644
--- a/tests/init.sh
+++ b/tests/init.sh
@@ -250,7 +250,7 @@ test -n "$BASH_VERSION" && unalias -a
# That is part of the s
