public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/115453] [15 regression] Noise from new dlopen, pthread configure checks since r15-1177-g75299e4fe50aa8
Date: Wed, 19 Jun 2024 13:10:35 +0000	[thread overview]
Message-ID: <bug-115453-4-qEmOV8WC83@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115453-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115453

Sam James <sjames at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |collin.funk1 at gmail dot com

--- Comment #11 from Sam James <sjames at gcc dot gnu.org> ---
commit r15-1436-gc6a9ab8c920f29
Author: Collin Funk <collin.funk1@gmail.com>
Date:   Thu Jun 13 17:53:55 2024 -0700

    build: Fix missing variable quotes

    When dlopen and pthread_create are in libc the variable is
    set to "none required", therefore running configure will show
    the following errors:

    ./configure: line 8997: test: too many arguments
    ./configure: line 8999: test: too many arguments
    ./configure: line 9003: test: too many arguments
    ./configure: line 9005: test: =: unary operator expected

    gcc/configure also has a similar problem on
    gcc_cv_as_mips_explicit_relocs:

    ./gcc/configure: line 30242: test: =: unary operator expected

    ChangeLog:

            * configure.ac: Quote variable result of AC_SEARCH_LIBS.
            * configure: Regenerate.

    gcc/ChangeLog:

            * configure.ac: Add missing quotation of variable
            gcc_cv_as_mips_explicit_relocs.
            * configure: Regenerate.

    Signed-off-by: Collin Funk <collin.funk1@gmail.com>

But the crate vs create needs fixing still.

  parent reply	other threads:[~2024-06-19 13:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12  2:58 [Bug other/115453] New: [15 regression] Noise from ne wdlopen, pthread configure checks sjames at gcc dot gnu.org
2024-06-12  2:58 ` [Bug other/115453] [15 regression] Noise from new dlopen, " sjames at gcc dot gnu.org
2024-06-12  3:01 ` [Bug bootstrap/115453] [15 regression] Noise from new dlopen, pthread configure checks since r15-1177-g75299e4fe50aa8 pinskia at gcc dot gnu.org
2024-06-12  3:02 ` pinskia at gcc dot gnu.org
2024-06-12  3:03 ` sjames at gcc dot gnu.org
2024-06-12  3:04 ` pinskia at gcc dot gnu.org
2024-06-12  3:07 ` pinskia at gcc dot gnu.org
2024-06-12  8:38 ` cohenarthur at gcc dot gnu.org
2024-06-12  8:40 ` cohenarthur at gcc dot gnu.org
2024-06-13 15:45 ` pinskia at gcc dot gnu.org
2024-06-13 15:46 ` cohenarthur at gcc dot gnu.org
2024-06-13 16:02 ` pinskia at gcc dot gnu.org
2024-06-19 13:10 ` sjames at gcc dot gnu.org [this message]
2024-06-19 14:33 ` cvs-commit at gcc dot gnu.org
2024-06-19 14:34 ` syq at gcc dot gnu.org
2024-06-19 20:29 ` collin.funk1 at gmail dot com
2024-06-19 22:34 ` mark at gcc dot gnu.org
2024-06-19 22:47 ` collin.funk1 at gmail dot com
2024-06-20  2:59 ` cvs-commit at gcc dot gnu.org

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=bug-115453-4-qEmOV8WC83@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.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).