From: Eric Blake <eblake@redhat.com>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: execute tests: Avoid test failure on Android
Date: Tue, 17 Jan 2023 13:42:01 -0600 [thread overview]
Message-ID: <20230117194201.mt6hsgxxwyjoyusv@redhat.com> (raw)
In-Reply-To: <4520176.VQJxnDRnGh@nimes>
On Tue, Jan 17, 2023 at 03:21:52PM +0100, Bruno Haible wrote:
> On Android 11, I'm seeing a test failure:
>
>
> Apparently the SIGPIPE handler gets set to SIG_IGN, either by 'make' or
> by the test-driver.
Known regression in make 4.4:
https://savannah.gnu.org/bugs/index.php?63307
and being fixed in 4.4.1, but it sounds like we'll have lots of
systems in the wild with 4.4, and thus lots of these workarounds
having to be applied elsewhere.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2023-01-17 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 14:21 execute tests: Avoid test failure on Android Bruno Haible
2023-01-17 19:42 ` Eric Blake [this message]
2023-01-17 21:15 ` Bruno Haible
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230117194201.mt6hsgxxwyjoyusv@redhat.com \
--to=eblake@redhat.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
/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).