From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: "Adhemerval Zanella" <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org, "Vineet Gupta" <vineetg@rivosinc.com>,
"Ludovic Courtès" <ludo@gnu.org>
Subject: Re: [PATCH 5/6] configure: Allow user override LD, AR, OBJCOPY, and GPROF
Date: Mon, 5 Dec 2022 10:56:58 -0500 [thread overview]
Message-ID: <3f7184fd-02e3-42f7-46de-b9f7e5fbbace@redhat.com> (raw)
In-Reply-To: <20221202190030.1671870-6-adhemerval.zanella@linaro.org>
On 12/2/22 14:00, Adhemerval Zanella via Libc-alpha wrote:
> The only way to override LD, AR, OBJCOPY, and GPROF is through
> --with-binutils (setting the environments variables on configure is
> overridden by LIBC_PROG_BINUTILS).
If this is true then doesn't build-many-glibcs.py need --with-binutils?
We set LD, AR, OBJCOPY in bmg (not GPROF though).
I'd think we'd either set them or let the defaults be used (remove their setting).
> ---
> aclocal.m4 | 16 ++++++++++++----
> configure | 16 ++++++++++++----
> 2 files changed, 24 insertions(+), 8 deletions(-)
>
> diff --git a/aclocal.m4 b/aclocal.m4
> index 7ab8ac023b..cbe3c4698a 100644
> --- a/aclocal.m4
> +++ b/aclocal.m4
> @@ -118,12 +118,20 @@ 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)
> -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)
> ])
OK.
>
> diff --git a/configure b/configure
> index 62c2581cb0..8f91bb6e11 100755
> --- a/configure
> +++ b/configure
Regenerate.
> @@ -4145,12 +4145,20 @@ 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
>
> -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
>
>
>
--
Cheers,
Carlos.
next prev parent reply other threads:[~2022-12-05 15:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 19:00 [PATCH 0/6] Refactor binutils configure usage Adhemerval Zanella via Libc-alpha
2022-12-02 19:00 ` [PATCH 1/6] configure: Move locale tools early Adhemerval Zanella via Libc-alpha
2022-12-05 15:56 ` Carlos O'Donell via Libc-alpha
2022-12-02 19:00 ` [PATCH 2/6] configure: Remove check if as is GNU Adhemerval Zanella via Libc-alpha
2022-12-05 15:56 ` Carlos O'Donell via Libc-alpha
2022-12-02 19:00 ` [PATCH 3/6] configure: Remove check if ld " Adhemerval Zanella via Libc-alpha
2022-12-05 15:56 ` Carlos O'Donell via Libc-alpha
2022-12-02 19:00 ` [PATCH 4/6] configure: Remove AS check Adhemerval Zanella via Libc-alpha
2022-12-05 15:56 ` Carlos O'Donell via Libc-alpha
2022-12-06 13:45 ` Andreas Schwab via Libc-alpha
2022-12-06 15:59 ` Adhemerval Zanella Netto via Libc-alpha
2022-12-02 19:00 ` [PATCH 5/6] configure: Allow user override LD, AR, OBJCOPY, and GPROF Adhemerval Zanella via Libc-alpha
2022-12-05 15:56 ` Carlos O'Donell via Libc-alpha [this message]
2022-12-07 20:04 ` Adhemerval Zanella Netto via Libc-alpha
2022-12-02 19:00 ` [PATCH 6/6] configure: Move nm, objdump, and readelf to LIBC_PROG_BINUTILS Adhemerval Zanella via Libc-alpha
2022-12-02 23:10 ` Rajalakshmi Srinivasaraghavan via Libc-alpha
2022-12-06 13:39 ` Adhemerval Zanella Netto via Libc-alpha
2022-12-05 15:57 ` Carlos O'Donell via Libc-alpha
2022-12-20 22:01 ` [PATCH 0/6] Refactor binutils configure usage Vineet Gupta
2022-12-22 12:54 ` Adhemerval Zanella Netto via Libc-alpha
2023-01-05 21:39 ` Vineet Gupta
2023-01-05 21:54 ` Adhemerval Zanella Netto via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3f7184fd-02e3-42f7-46de-b9f7e5fbbace@redhat.com \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=ludo@gnu.org \
--cc=vineetg@rivosinc.com \
/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).