Hi,
I was wondering if the following changes I made to findutils (to get it to
function on z/OS) can be merged into gnulib.
The first change (fdopendir.c) guards the close call. Otherwise we get a bad
file descriptor on z/OS. I am not sure if this has any other consequences, but
so far I haven
The sc_copyright_check syntax check is hitting me badly, due to an incorrect
determination of 'gnulib_dir' in maint.mk.
What I've done is:
- set GNULIB_SRCDIR to point to my current Gnulib checkout,
- checked out GNU grep from git,
- ran './bootstrap --gnulib-srcdir=$GNULIB_SRCDIR --no-git'
On 2023-01-29 15:20, Bruno Haible wrote:
Notice in particular:
- the different definitions of __CONCAT
- the different definitions of __inline
- the different definitions of __always_inline
- the different definitions of __warnattr
I would not be surprised if these macros cause troub
Hi Paul,
I wrote:
> The cause is that Android has its own framework for defining fortified
> variants of the string operations, and like glibc it uses macros named
> '__bos' and '__bos0'. But these macros have different definitions in
> Android than in glibc.
This situation can happen with any sy
On Android, clang does not define _FORTIFY_SOURCE by default, but the Android
NDK sets CC to something like "clang -D_FORTIFY_SOURCE=2". Then, we see
compilation errors, such as
clang -ferror-limit=0 -D_FORTIFY_SOURCE=2 -DHAVE_CONFIG_H -DEXEEXT=\"\"
-DEXEEXT=\"\" -DNO_XMALLOC -DEXEEXT=\"\" -I. -I
