public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Iain D Sandoe <iains@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-5278] Darwin, libffi, testsuite: Ensure we pick up the convenience lib.
Date: Sun, 22 Jan 2023 09:33:13 +0000 (GMT)	[thread overview]
Message-ID: <20230122093313.36C173858D32@sourceware.org> (raw)

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

commit r13-5278-ge4703bd0e15b4ed6e5eae36604b28bd4ca4f8cee
Author: Iain Sandoe <iain@sandoe.co.uk>
Date:   Sat Jan 21 19:52:58 2023 +0000

    Darwin, libffi, testsuite: Ensure we pick up the convenience lib.
    
    For several Darwin linker versions, the link paths are first traversed
    looking for shared libraries, and then again looking for archives.
    
    We want the paths to be searched for both shared and archives in order
    so that we will find the non-shared libffi in the testsuite (otherwise
    the installed version in the system will be found instead).
    
    Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>
    
    libffi/ChangeLog:
    
            * testsuite/lib/libffi.exp: Search for both shared and archive
            in each path in turn.

Diff:
---
 libffi/testsuite/lib/libffi.exp | 1 +
 1 file changed, 1 insertion(+)

diff --git a/libffi/testsuite/lib/libffi.exp b/libffi/testsuite/lib/libffi.exp
index 7dc7b5d19a3..15d3d5ebd73 100644
--- a/libffi/testsuite/lib/libffi.exp
+++ b/libffi/testsuite/lib/libffi.exp
@@ -384,6 +384,7 @@ proc libffi_target_compile { source dest type options } {
     if { [istarget "*-*-darwin9*"] || [istarget "*-*-darwin1*"]
 	 || [istarget "*-*-darwin2*"] } {
 	lappend options "additional_flags=-Wl,-allow_stack_execute"
+	lappend options "additional_flags=-Wl,-search_paths_first"
     }
 
     # If you're building the compiler with --prefix set to a place

                 reply	other threads:[~2023-01-22  9:33 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=20230122093313.36C173858D32@sourceware.org \
    --to=iains@gcc.gnu.org \
    --cc=gcc-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).