bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Nick Bowler <nbowler@draconx.ca>
To: bug-gnulib@gnu.org
Subject: [PATCH] threadlib: fix case patterns for older Solaris.
Date: Tue, 24 Jan 2023 22:53:45 -0500	[thread overview]
Message-ID: <20230125035345.26562-1-nbowler@draconx.ca> (raw)

The case pattern which matches solaris2.[1-9] etc. is not fully
quoted, so the brackets get eaten by m4 and don't actually make
it into the resulting configure script, giving just:

    case "$host_os" in
      solaris | solaris2.1-9 | solaris2.1-9.* | hpux*)

which is obviously not correct.

* m4/threadlib.m4 (gl_STDTHREADLIB_BODY): Allow case patterns to
survive m4 processing by using changequote.
---
 m4/threadlib.m4 | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/m4/threadlib.m4 b/m4/threadlib.m4
index 48ced460b3..49bc99ef3b 100644
--- a/m4/threadlib.m4
+++ b/m4/threadlib.m4
@@ -261,7 +261,9 @@ AC_DEFUN([gl_PTHREADLIB_BODY],
              # On Solaris 10 or newer, this test is no longer needed, because
              # libc contains the fully functional pthread functions.
              case "$host_os" in
+changequote(,)dnl
                solaris | solaris2.[1-9] | solaris2.[1-9].* | hpux*)
+changequote([,])dnl
                  AC_DEFINE([PTHREAD_IN_USE_DETECTION_HARD], [1],
                    [Define if the pthread_in_use() detection is hard.])
              esac
-- 
2.35.1



             reply	other threads:[~2023-01-25  3:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25  3:53 Nick Bowler [this message]
2023-01-25  8:44 ` [PATCH] threadlib: fix case patterns for older Solaris 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=20230125035345.26562-1-nbowler@draconx.ca \
    --to=nbowler@draconx.ca \
    --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).