Bruno Haible writes:
> Po Lu wrote:
>> stpncpy is not replaced when building with the Android NDK r25b and
>> __ANDROID_API__ 19, since it is __INTRODUCED_IN (21).
>>
>> I guess this should be fixed. Thanks.
>
> This ought to be done through commits from 2023-0
Po Lu wrote:
> stpncpy is not replaced when building with the Android NDK r25b and
> __ANDROID_API__ 19, since it is __INTRODUCED_IN (21).
>
> I guess this should be fixed. Thanks.
This ought to be done through commits from 2023-01-19 and 2023-01-22.
If it does not work for you, in
stpncpy is not replaced when building with the Android NDK r25b and
__ANDROID_API__ 19, since it is __INTRODUCED_IN (21).
I guess this should be fixed. Thanks.
Hi,
Jeremy Huddleston recently reported a build failure of gettext on some
not-yet-released FreeBSD based system, due to the gnulib stpncpy module.
On that system, stpncpy is defined as a "complex macro", causing
1) the gl_FUNC_STPNCPY macro to think that stpncpy does not work
On mingw, with warn-on-use.h modified to simulate a gcc >= 4.3, I'm seeing this
error:
In file included from test-string-c++.cc:22:
../gllib/string.h:525: error: `stpncpy' was not declared in this scope
The reason is that the 'stpncpy' module uses
#define stpncpy
David Lutterkort wrote:
> would it be possible to relicense stpncpy (currently LGPL) as LGPLv2+ ?
Yes. This is possible, since lib/stpncpy.c originally came from glibc and
was not modified since the switch from LGPLv2+ to LGPLv3+ two years ago.
2009-10-21 Bruno Haible
* modu
Hi,
would it be possible to relicense stpncpy (currently LGPL) as LGPLv2+ ?
I want to use it in Augeas, which is LGPLv2+.
David
