From: Sergei Trofimovich <slyich@gmail.com>
To: lloda <lloda@sarc.name>
Cc: 49930@debbugs.gnu.org
Subject: bug#49930: glibc-2.34 build failure in gnulib (needs a sync)
Date: Mon, 16 Aug 2021 19:25:32 +0100 [thread overview]
Message-ID: <20210816192532.473d2bc6@zn3> (raw)
In-Reply-To: <643A4A6B-FF10-4373-9C03-1A393B253935@sarc.name>
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
On Mon, 16 Aug 2021 19:41:36 +0200
lloda <lloda@sarc.name> wrote:
> Hi,
>
> I have updated gnulib in http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commitdiff;h=b4a80f4239b19fea4d2cc3e9d197f24b809f0624 <http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commitdiff;h=b4a80f4239b19fea4d2cc3e9d197f24b809f0624>. Please let me know if this solves the issue – I am unable to test with the newer glibc versions.
The change fixes build for me and passes all except one test:
test-suite/standalone/test-out-of-memory
which is unrelated to glibc-2.34.
Definitely an improvement.
Thank you!
--
Sergei
[-- Attachment #2: Цифровая подпись OpenPGP --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
prev parent reply other threads:[~2021-08-16 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 19:40 bug#49930: glibc-2.34 build failure in gnulib (needs a sync) Sergei Trofimovich
2021-08-16 17:41 ` lloda
2021-08-16 18:25 ` Sergei Trofimovich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210816192532.473d2bc6@zn3 \
--to=slyich@gmail.com \
--cc=49930@debbugs.gnu.org \
--cc=lloda@sarc.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).