public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Simon Marchi <simark@sourceware.org>
To: bfd-cvs@sourceware.org, gdb-cvs@sourceware.org
Subject: [binutils-gdb] Re-apply "Pass PKG_CONFIG_PATH down from top-level Makefile"
Date: Wed, 12 Oct 2022 03:09:48 +0000 (GMT)	[thread overview]
Message-ID: <20221012030948.0A5283856DC8@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9e65489ac29a2b38417c4f17acf82187343751a6

commit 9e65489ac29a2b38417c4f17acf82187343751a6
Author: Simon Marchi <simon.marchi@efficios.com>
Date:   Fri Apr 8 10:56:41 2022 -0400

    Re-apply "Pass PKG_CONFIG_PATH down from top-level Makefile"
    
    Commit 228cf97dd3c8 ("Merge configure.ac from gcc project") undid the
    change originally done in de83289ef32e ("Pass PKG_CONFIG_PATH down from
    top-level Makefile").  Re-apply it.
    
    Change-Id: I91138dfca41c43b05e53e445f62e4b27882536bf

Diff:
---
 configure    | 2 ++
 configure.ac | 1 +
 2 files changed, 3 insertions(+)

diff --git a/configure b/configure
index 4d328b735a3..9ea8034f5d7 100755
--- a/configure
+++ b/configure
@@ -621,6 +621,7 @@ CXX_FOR_TARGET
 CC_FOR_TARGET
 RANLIB_PLUGIN_OPTION
 AR_PLUGIN_OPTION
+PKG_CONFIG_PATH
 GDCFLAGS
 READELF
 OTOOL
@@ -12932,6 +12933,7 @@ fi
 
 
 
+
 { $as_echo "$as_me:${as_lineno-$LINENO}: checking for -plugin option" >&5
 $as_echo_n "checking for -plugin option... " >&6; }
 
diff --git a/configure.ac b/configure.ac
index 47931ff4e9e..8af83cc98d3 100644
--- a/configure.ac
+++ b/configure.ac
@@ -3654,6 +3654,7 @@ AC_SUBST(CFLAGS)
 AC_SUBST(CXXFLAGS)
 AC_SUBST(GDC)
 AC_SUBST(GDCFLAGS)
+AC_SUBST(PKG_CONFIG_PATH)
 
 GCC_PLUGIN_OPTION(PLUGIN_OPTION)
 AR_PLUGIN_OPTION=

                 reply	other threads:[~2022-10-12  3:09 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=20221012030948.0A5283856DC8@sourceware.org \
    --to=simark@sourceware.org \
    --cc=bfd-cvs@sourceware.org \
    --cc=gdb-cvs@sourceware.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).