From: "Ludovic Courtès" <ludo@gnu.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: branch master updated: gnu: gettext-minimal: Mark "test-raise" test XFAIL on the Hurd.
Date: Mon, 12 Oct 2020 12:10:50 +0200 [thread overview]
Message-ID: <87sgaju53p.fsf@gnu.org> (raw)
In-Reply-To: <87h7r82740.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Mon, 05 Oct 2020 14:24:31 +0200")
Hi!
Jan Nieuwenhuizen <janneke@gnu.org> skribis:
>> commit 2fc298d19c5256eb5609aae7bd35bada59d91685
>> Author: Jan (janneke) Nieuwenhuizen <janneke@gnu.org>
>> AuthorDate: Mon Oct 5 11:58:16 2020 +0200
>>
>> gnu: gettext-minimal: Mark "test-raise" test XFAIL on the Hurd.
>>
>> * gnu/packages/gettext.scm (gettext-minimal)[arguments]: When compiling for
>> the Hurd, add "test-raise" to XFAIL_TESTS in make-flags.
>
> Some more info on this bug, it is this snippet that causes
> the test failure
>
> #include <signal.h>
>
> int
> main (void)
> {
> if (!raise (-1))
> return 1;
>
> return 0;
> }
>
>
> but only when linked against libpthread:
>
> $ gcc raise.c
> $ ./a.out
> $ echo $?
> 0
> $ gcc raise.c /gnu/store/9vs3gkp6svam82zw7vjlml7iiarcs11c-glibc-2.31/lib/libpthread.so.0.3
I don’t know if it’s relevant here, but you should always use ‘-pthread’
both at compile time and link time:
gcc raise.c -pthread
That typically defines a few macros that may or may not have an effect
on the code at hand.
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-10-12 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201005100249.19995.93553@vcs0.savannah.gnu.org>
2020-10-05 12:24 ` branch master updated: gnu: gettext-minimal: Mark "test-raise" test XFAIL on the Hurd Jan Nieuwenhuizen
2020-10-05 12:27 ` Efraim Flashner
2020-10-12 10:10 ` Ludovic Courtès [this message]
2020-10-12 11:37 ` Jan Nieuwenhuizen
2020-10-13 13:41 ` raise(-1) succeeds for programs linked against libpthread Ludovic Courtès
2020-10-13 13:57 ` Samuel Thibault
2020-10-13 20:41 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgaju53p.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=janneke@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.