public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Adhemerval Zanella <azanella@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc/azanella/clang] Use AR, LD, OBJDUMP, OJBCOPY, and GPROF if there are set at configure
Date: Fri, 28 Oct 2022 17:42:46 +0000 (GMT)	[thread overview]
Message-ID: <20221028174246.5AE863857833@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=5e7ca48ca0c0929b449f194a71f33c0e6c3b4fd3

commit 5e7ca48ca0c0929b449f194a71f33c0e6c3b4fd3
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Thu Aug 4 16:43:17 2022 -0300

    Use AR, LD, OBJDUMP, OJBCOPY, and GPROF if there are set at configure

Diff:
---
 aclocal.m4 | 20 +++++++++++++++-----
 configure  | 20 +++++++++++++++-----
 2 files changed, 30 insertions(+), 10 deletions(-)

diff --git a/aclocal.m4 b/aclocal.m4
index 94c931b4f2..01afd73239 100644
--- a/aclocal.m4
+++ b/aclocal.m4
@@ -118,14 +118,24 @@ case "$CC" in
     *fuse-ld=lld*) LDNAME=ld.lld;;
     *)             LDNAME=ld;;
 esac
-LD=`$CC -print-prog-name=$LDNAME`
-AR=`$CC -print-prog-name=ar`
+if test -z "$LD"; then
+  LD=`$CC -print-prog-name=$LDNAME`
+fi
+if test -z "$AR"; then
+  AR=`$CC -print-prog-name=ar`
+fi
 AC_SUBST(AR)
-OBJDUMP=`$CC -print-prog-name=objdump`
+if test -z "$OBJDUMP"; then
+  OBJDUMP=`$CC -print-prog-name=objdump`
+fi
 AC_SUBST(OBJDUMP)
-OBJCOPY=`$CC -print-prog-name=objcopy`
+if test -z "$OBJCOPY"; then
+  OBJCOPY=`$CC -print-prog-name=objcopy`
+fi
 AC_SUBST(OBJCOPY)
-GPROF=`$CC -print-prog-name=gprof`
+if test -z "$GPROF"; then
+  GPROF=`$CC -print-prog-name=gprof`
+fi
 AC_SUBST(GPROF)
 
 # Determine whether we are using GNU binutils.
diff --git a/configure b/configure
index 3476e62ee7..03fceee905 100755
--- a/configure
+++ b/configure
@@ -4575,14 +4575,24 @@ case "$CC" in
     *fuse-ld=lld*) LDNAME=ld.lld;;
     *)             LDNAME=ld;;
 esac
-LD=`$CC -print-prog-name=$LDNAME`
-AR=`$CC -print-prog-name=ar`
+if test -z "$LD"; then
+  LD=`$CC -print-prog-name=$LDNAME`
+fi
+if test -z "$AR"; then
+  AR=`$CC -print-prog-name=ar`
+fi
 
-OBJDUMP=`$CC -print-prog-name=objdump`
+if test -z "$OBJDUMP"; then
+  OBJDUMP=`$CC -print-prog-name=objdump`
+fi
 
-OBJCOPY=`$CC -print-prog-name=objcopy`
+if test -z "$OBJCOPY"; then
+  OBJCOPY=`$CC -print-prog-name=objcopy`
+fi
 
-GPROF=`$CC -print-prog-name=gprof`
+if test -z "$GPROF"; then
+  GPROF=`$CC -print-prog-name=gprof`
+fi
 
 
 # Determine whether we are using GNU binutils.

             reply	other threads:[~2022-10-28 17:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28 17:42 Adhemerval Zanella [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-04 13:00 Adhemerval Zanella

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=20221028174246.5AE863857833@sourceware.org \
    --to=azanella@sourceware.org \
    --cc=glibc-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).