From: "Tom G. Christensen" <tgc@jupiterrise.com>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Subject: Re: Remove support for old Solaris threads
Date: Mon, 8 Jul 2019 19:30:38 +0200 [thread overview]
Message-ID: <9ee84716-f8d9-4add-e8d8-b67038789cbe@jupiterrise.com> (raw)
In-Reply-To: <8954166.HdCVRHMRbA@omega>
On 06/07/19 03:38, Bruno Haible wrote:
> The old Solaris threads facility was needed for portability to the
> ancient Solaris 2.4. Solaris >= 2.5.1 has POSIX threads.
Do note though that since you changed the witness symbol in 0f336e1192
the gnulib POSIX thread support has been unbuildable on Solaris < 7.
Just to see what state it's in on Solaris 2.6 I changed the witness back
to pthread_cancel and created a testdir with:
./gnulib-tool --dir ../thread-test --with-tests --create-testdir pthread
cond tls lock thrd
This resulted in:
...
test-once.c:40: assertion 'a == 42' failed
/bin/bash: line 5: 26049 Abort (core dumped) EXEEXT=''
srcdir='.' MAKE='make' ${dir}$tst
FAIL: test-once1
...
test-nanosleep.c:62: assertion 'ts.tv_sec == 0' failed
/bin/bash: line 5: 26065 Abort (core dumped) EXEEXT=''
srcdir='.' MAKE='make' ${dir}$tst
FAIL: test-nanosleep
...
FAIL: test-select-in.sh
...
====================
3 of 94 tests failed
====================
FWIW I don't think any of these are new for Solaris 2.6.
-tgc
next prev parent reply other threads:[~2019-07-08 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 1:38 Remove support for old Solaris threads Bruno Haible
2019-07-08 17:30 ` Tom G. Christensen [this message]
2019-07-08 21:50 ` Paul Eggert
2019-07-08 23:24 ` 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=9ee84716-f8d9-4add-e8d8-b67038789cbe@jupiterrise.com \
--to=tgc@jupiterrise.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).