Bruno Haible writes:
> Correct. We don't want to force 'git submodule' into everyone's throat.
>
> By the way, the cases of with / without submodules are treated symmetrically
> (transparently) in gitsub.sh (gnulib/top/gitsub.sh). I've switched to using
> this helper script in my projects, so tha
Bruno Haible writes:
> Hi Simon,
>
>> The reason is top/maint.mk has
>>
>> # You can override this variable in cfg.mk if your gnulib submodule lives
>> # in a different location.
>> gnulib_dir ?= $(srcdir)/gnulib
>>
>> and that directory doesn't exist if bootstrap used $GNULIB_SRCDIR.
>
> In
Paul Eggert writes:
> On 1/25/21 7:55 PM, Jeffrey Walton wrote:
>
>>> Jeffrey Walton wrote:
Placing flags in CC breaks other scripts. For example, this no longer
works:
if [[ ! $(command -v "${CC}") ]]; then
echo "The compiler is not valid. Please install a
Hi! I've noticed in a couple of projects that use bootstrap, without a
gnulib git submodule, and where $GNULIB_SRCDIR is set during bootstrap,
that syntax-check will print some spurious errors like this:
prohibit_intprops_without_use
Can't open ./gnulib/lib/intprops.h: Filen eller katalogen finns
Hi. There were discussion about libidn/libidn2 support for GNU
InetUtils, and today I believe the recommended way for GNU applications
is to use system getaddrinfo for IDN functionality and not link to
libidn/libidn2 directly. This works fine on modern glibc systems, and
using it reduces complexi
> The 'Link' section in the module description is only informative.
>
> Originally, we thought that it would be good to note, in the 'Link'
> section,
> only the immediate link dependencies of the module, and let the user
> use
> ./gnulib-tool --extract-recursive-link-directive MODULE
> for the
Bruno Haible writes:
> Hi Simon,
>
>> Hi. I re-read the discussion around getrandom vs gc-random and didn't
>> see any point in keeping the duplicated code. I believe the
>> getrandom-approach is better than what was in gc-gnulib.c today, so this
>> patch make it use that function. I have push
Hi. I re-read the discussion around getrandom vs gc-random and didn't
see any point in keeping the duplicated code. I believe the
getrandom-approach is better than what was in gc-gnulib.c today, so this
patch make it use that function. I have pushed the patch below.
/Simon
From 44ed0db8c93f6a81