public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Iain D Sandoe <iains@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r14-9542] libstdc++: Sync the atomic_link_flags implementation with GCC.
Date: Tue, 19 Mar 2024 12:54:15 +0000 (GMT)	[thread overview]
Message-ID: <20240319125415.EC667385840E@sourceware.org> (raw)

https://gcc.gnu.org/g:71a44faa8a4f76d68356c66c6054e6c242df820f

commit r14-9542-g71a44faa8a4f76d68356c66c6054e6c242df820f
Author: Iain Sandoe <iain@sandoe.co.uk>
Date:   Mon Mar 18 09:57:33 2024 +0000

    libstdc++: Sync the atomic_link_flags implementation with GCC.
    
    For Darwin, in order to allow uninstalled testing, we need to provide
    a '-B' option pointing to each path containing an uninstalled library
    that we are using (these get appended to the embedded runpaths).
    
    This updates the version of the atomic_link_flags proc in the libstdc++
    testsuite to do the same as the one in the GCC testsuite.
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/lib/dg-options.exp (atomic_link_flags): Emit a -B
            option for the path to the uninstalled libatomic.
    
    Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>

Diff:
---
 libstdc++-v3/testsuite/lib/dg-options.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/lib/dg-options.exp b/libstdc++-v3/testsuite/lib/dg-options.exp
index bc387d17ed7..00ca678a53a 100644
--- a/libstdc++-v3/testsuite/lib/dg-options.exp
+++ b/libstdc++-v3/testsuite/lib/dg-options.exp
@@ -314,7 +314,7 @@ proc atomic_link_flags { paths } {
       if { [file exists "${gccpath}/libatomic/.libs/libatomic.a"]
            || [file exists "${gccpath}/libatomic/.libs/libatomic.${shlib_ext}"] } {
           append flags " -B${gccpath}/libatomic/ "
-          append flags " -L${gccpath}/libatomic/.libs"
+          append flags " -B${gccpath}/libatomic/.libs"
           append ld_library_path ":${gccpath}/libatomic/.libs"
       }
     } else {

                 reply	other threads:[~2024-03-19 12:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240319125415.EC667385840E@sourceware.org \
    --to=iains@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).