From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
To: Alan Modra <amodra@gmail.com>, binutils@sourceware.org
Subject: Re: gprofng configure target tests
Date: Thu, 17 Mar 2022 11:20:14 -0700 [thread overview]
Message-ID: <a95c476a-4204-61ae-8796-33cf19c1ce67@oracle.com> (raw)
In-Reply-To: <YjMUqWgoUA6T+Cfl@squeak.grove.modra.org>
Hi Alan,
Please check in your patch.
Thank you,
-Vladimir
On 3/17/22 03:59, Alan Modra via Binutils wrote:
> ${target} in configure.ac should be the canonical target, so that for
> example, someone configuring with --target=x86_64-linux will match
> x86_64-*-linux*.
>
> * configure.ac: Invoke AC_CANONICAL_TARGET.
> * libcollector/configure.ac: Likewise.
> * Makefile.in: Regenerate.
> * configure: Regenerate.
> * doc/Makefile.in: Regenerate.
> * gp-display-html/Makefile.in: Regenerate.
> * libcollector/Makefile.in: Regenerate.
> * libcollector/configure: Regenerate.
> * src/Makefile.in: Regenerate.
>
> diff --git a/gprofng/configure.ac b/gprofng/configure.ac
> index 23fee8705ac..c05e98192f3 100644
> --- a/gprofng/configure.ac
> +++ b/gprofng/configure.ac
> @@ -18,6 +18,7 @@ dnl <http://www.gnu.org/licenses/>.
>
> m4_include([../bfd/version.m4])
> AC_INIT([gprofng], BFD_VERSION)
> +AC_CANONICAL_TARGET
> AM_INIT_AUTOMAKE([subdir-objects])
> AM_MAINTAINER_MODE
>
> diff --git a/gprofng/libcollector/configure.ac b/gprofng/libcollector/configure.ac
> index d82733fbc39..1da916ef83c 100644
> --- a/gprofng/libcollector/configure.ac
> +++ b/gprofng/libcollector/configure.ac
> @@ -20,6 +20,7 @@ m4_include([../../bfd/version.m4])
> AC_INIT([gprofng], BFD_VERSION)
> AC_CONFIG_MACRO_DIRS([../../config ../..])
> AC_CONFIG_AUX_DIR(../..)
> +AC_CANONICAL_TARGET
> AM_INIT_AUTOMAKE
> AM_MAINTAINER_MODE
>
>
prev parent reply other threads:[~2022-03-17 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 10:59 Alan Modra
2022-03-17 18:20 ` Vladimir Mezentsev [this message]
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=a95c476a-4204-61ae-8796-33cf19c1ce67@oracle.com \
--to=vladimir.mezentsev@oracle.com \
--cc=amodra@gmail.com \
--cc=binutils@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).