Re: unlink-busy does not support cross-compilation

2019-03-23 Thread Bruno Haible
Jim Meyering wrote: > What do you think about using the existing run-test code when possible, > but to resort to using that hard-coded list when cross-compiling? > That way, the code adapts well (at least in some cases) when it finds > a new type of system for which this is applicable. Possible.

Re: unlink-busy does not support cross-compilation

2019-03-23 Thread Jim Meyering
On Sat, Mar 23, 2019 at 10:26 AM Bruno Haible wrote: > Hi Jim, > > The module 'unlink-busy' does not support cross-compilation: It uses > AC_RUN_IFELSE, thus calling the compiler for the host, and then sets > INSTALL, which is meant to point to a command to execute on the build machine. > > It sho

Re: While cross compiling, assume the gcc signbit support for the musl as well

2019-03-23 Thread Necktwi Ozfguah
Thank You. ... Necktwi

Re: While cross compiling, assume the gcc signbit support for the musl as well

2019-03-23 Thread Bruno Haible
Hi, > while cross building, signbit support is assumed with glibc > so should be with musl. You are right that gnulib should care about cross-compilation to musl systems. Reason: It's one of the main options when using 'buildroot', see https://buildroot.org/downloads/manual/manual.html#_cross_com

posix_spawn_file_actions_add* functions on musl libc

2019-03-23 Thread Bruno Haible
The gnulib configure test in m4/posix_spawn.m4, when run on Alpine Linux 3.7, determines that the posix_spawn_file_actions_add* functions do not fail as expected for an out-of-range file descriptor. Let me document this in gnulib and update the cross-compilation guess accordingly. Rich, FYI: Thes

futimens on musl libc

2019-03-23 Thread Bruno Haible
The gnulib configure test in m4/futimens.m4, when run on Alpine Linux 3.7, determines that the errno value is not as expected for a wrong fd. Let me document this in gnulib and update the cross-compilation guess accordingly. Rich, FYI: The test program is this one: #include #include #include

flag cross-compilation guesses are guesses

2019-03-23 Thread Bruno Haible
When a configure test's result is merely a guess, not a determined fact, it's a good practice to flag it as a guess in the 'configure' output. Let's do so in a couple of more places. 2019-03-23 Bruno Haible Clarify that cross-compilation guesses are guesses. * m4/chown.m4 (gl_

strtold: Fix typo

2019-03-23 Thread Bruno Haible
A small copy-and-paste mistake, visible only when cross-compiling. 2019-03-23 Bruno Haible strtold: Fix typo. * m4/strtold.m4 (gl_FUNC_STRTOLD): Fix typo in variable name. diff --git a/m4/strtold.m4 b/m4/strtold.m4 index c1c05d1..16b4eda 100644 --- a/m4/strtold.m4 +++ b/m4/st

Re: undefined behaviour findings in bitset

2019-03-23 Thread Bruno Haible
Hi Akim, > it does not work with G++ in C++98 mode: _Noreturn is not supported there. I confirm: No g++ version I tested supported _Noreturn, neither with -std=c++98 nor with -std=c++11. Your patch looks good. > Using C's _Noreturn in C++98 appears to be supported by Clang Good point! Let me a

unlink-busy does not support cross-compilation

2019-03-23 Thread Bruno Haible
Hi Jim, The module 'unlink-busy' does not support cross-compilation: It uses AC_RUN_IFELSE, thus calling the compiler for the host, and then sets INSTALL, which is meant to point to a command to execute on the build machine. It should IMO better use the compiler for the build machine, but this is

Re: bug#34951: [PATCH] grep: a kwset matcher not work in a grep matcher

2019-03-23 Thread Eric Blake
On 3/22/19 9:59 PM, Budi wrote: > How make grep walking through FS by scanning breadth first instead of > > On 3/23/19, Budi wrote: >> How make grep walinh through FS by scanning breadth first instead of >> the usual depth >> >> On 3/23/19, Norihiro Tanaka wrote: >>> On Sat, 23 Mar 2019 08:06:35