From: ludo@gnu.org (Ludovic Courtès)
To: Greg Troxel <gdt@ir.bbn.com>
Cc: guile-devel@gnu.org
Subject: TLS support on NetBSD
Date: Fri, 23 Oct 2009 10:36:20 +0200 [thread overview]
Message-ID: <878wf2tsl7.fsf@gnu.org> (raw)
Hi Greg,
NetBSD builds have been failing since the introduction of TLS support
(http://autobuild.josefsson.org/guile/log-200910220603170256000.txt):
gcc -I/usr/pkg/include -I/usr/y0/include -Wall -Wmissing-prototypes -Werror -fvisibility=hidden -I/usr/pkg/include -g -O2 -I/usr/pkg/include -I/usr/y0/include -o .libs/guile guile-guile.o -L/usr/pkg/lib -L/usr/y0/lib ./.libs/libguile.so /usr/pkg/lib/libintl.so -lc /usr/pkg/lib/libgmp.so /usr/pkg/lib/libgc.so -lpthread -lrt /usr/y0/lib/libunistring.so -lcrypt -lm /usr/pkg/lib/libltdl.so -Wl,--rpath -Wl,/usr/local/lib -Wl,--rpath -Wl,/usr/pkg/lib -Wl,--rpath -Wl,/usr/y0/lib
./.libs/libguile.so: warning: warning: tmpnam() possibly used unsafely, use mkstemp() or mkdtemp()
./.libs/libguile.so: undefined reference to `__tls_get_addr'
This looks as though TLS was not actually implemented in NetBSD’s libc.
Do you have any info on this?
Besides, I was hoping that
http://git.savannah.gnu.org/cgit/guile.git/commit/?id=96e15df109ccfdcc2f6b2cffc0b64a083f000903
would fix NetBSD builds, but apparently that’s not enough. Any
suggestion to fix it?
Thanks,
Ludo’.
next reply other threads:[~2009-10-23 8:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 8:36 Ludovic Courtès [this message]
2009-10-23 23:40 ` TLS support on NetBSD Greg Troxel
2009-10-29 19:18 ` Ken Raeburn
2009-10-29 22:24 ` Ludovic Courtès
2009-10-29 22:53 ` Ken Raeburn
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=878wf2tsl7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=gdt@ir.bbn.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).