public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112864] [14 regression] Many libphobos tests FAIL on macOS 12+
Date: Fri, 02 Feb 2024 09:02:13 +0000	[thread overview]
Message-ID: <bug-112864-4-B7ClsW0Ezg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112864-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>:

https://gcc.gnu.org/g:f4aa644dbbbde8c97f41c8abfbb7925c2242e31f

commit r14-8734-gf4aa644dbbbde8c97f41c8abfbb7925c2242e31f
Author: Iain Sandoe <iain@sandoe.co.uk>
Date:   Sat Jan 27 15:50:15 2024 +0000

    testsuite, libphobos: Update link flags [PR112864].

    The regressions here are primarily from duplicated '-B' additions.

    We remove the duplicate on the link line.
    We also make sure that platforms with extensions other than .so for
    shared libs will have the correct paths.

            PR target/112864

    libphobos/ChangeLog:

            * testsuite/lib/libphobos.exp: Use ${shlib_ext} instead of
            hard-wiring '.so'.
            * testsuite/testsuite_flags.in: Remove duplicate -B option
            for spec file path.

  parent reply	other threads:[~2024-02-02  9:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 12:55 [Bug target/112864] New: " ro at gcc dot gnu.org
2023-12-05 12:56 ` [Bug target/112864] " ro at gcc dot gnu.org
2024-01-28 15:18 ` iains at gcc dot gnu.org
2024-02-02  9:02 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-02  9:05 ` iains at gcc dot gnu.org
2024-02-10 15:24 ` [Bug target/112864] " iains at gcc dot gnu.org
2024-05-07  7:43 ` rguenth 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-112864-4-B7ClsW0Ezg@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).