From: ludo@gnu.org (Ludovic Courtès)
To: "Chris K. Jester-Young" <cky944@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Fixing srfi-18.test when building on OS X with clang
Date: Tue, 02 Dec 2014 21:34:30 +0100 [thread overview]
Message-ID: <87lhmpaizt.fsf@gnu.org> (raw)
In-Reply-To: <20141130083314.GA13994@lotus.destinee.acro.gen.nz> (Chris K. Jester-Young's message of "Sun, 30 Nov 2014 03:33:14 -0500")
"Chris K. Jester-Young" <cky944@gmail.com> skribis:
> The basic purpose of the patch is to disable thread-local storage when
> building on OS X. This is probably clang-specific, but I don't have
> enough autotools-fu to check for that. In any case, when using TLS, the
> value of (current-thread) is not always correctly maintained, which
> then causes srfi-18.test to fail.
I could try to come up with an Autoconf test for ‘__thread’, but what’s
the exact problem? Is it that TLS in general doesn’t work (that sounds
unlikely)? Or is it that TLS is inaccessible from a pthread_atexit
handler or something like that?
Thanks,
Ludo’.
prev parent reply other threads:[~2014-12-02 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 8:33 [PATCH] Fixing srfi-18.test when building on OS X with clang Chris K. Jester-Young
2014-12-02 20:34 ` Ludovic Courtès [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=87lhmpaizt.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cky944@gmail.com \
--cc=guile-devel@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).