Hello,
We pull down libidn and libidn2, both of which rely on gnulib and we have
with some increasing frequency seen remote out of memory errors. I saw from
the prior issues other people have had that we should contact this mailing
list if we need some assistance:
remote: fatal: Out of memory, ma
Hi
Not really a solution to the savannah malloc failures (I've been seeing
them too when pulling gnulib 10x in parallel from savannah during
continous integration pipeline jobs) but a note that I am (as
libidn/libidn2 maintainer) considering to not use a gnulib submodule but
rather rely on ./boots
We have been looking at trying to configure libidn to use a prebuild.. We
had some issues, but not enough time to figure out what failed yet. I will
add that our builds fail on the clone with a -j1 logic or -j 12 ( ie N )
equally.
As far as your questions, I am not sure. I am just adding in some No
Hello Phong,
Phong X. Nguyen wrote:
> We pull down libidn and libidn2, both of which rely on gnulib and we have
> with some increasing frequency seen remote out of memory errors. I saw from
> the prior issues other people have had that we should contact this mailing
> list if we need some assistan
Hi Simon,
Simon Josefsson wrote:
> Not really a solution to the savannah malloc failures (I've been seeing
> them too when pulling gnulib 10x in parallel from savannah during
> continous integration pipeline jobs) but a note that I am (as
> libidn/libidn2 maintainer) considering to not use a gnuli
Hi Jason,
Jason Kenny wrote:
> We have been looking at trying to configure libidn to use a prebuild.. We
> had some issues, but not enough time to figure out what failed yet. I will
> add that our builds fail on the clone with a -j1 logic or -j 12 ( ie N )
> equally.
> As far as your questions, I
