public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Vladimir Mezentsev <vmezents@sourceware.org> To: bfd-cvs@sourceware.org, gdb-cvs@sourceware.org Subject: [binutils-gdb] gprofng: fix typo in configure.ac Date: Fri, 11 Nov 2022 01:25:46 +0000 (GMT) [thread overview] Message-ID: <20221111012546.BF14C3858D1E@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=1c343a13ba24eb2dad39a94df1a369a0f62efd13 commit 1c343a13ba24eb2dad39a94df1a369a0f62efd13 Author: Vladimir Mezentsev <vladimir.mezentsev@oracle.com> Date: Thu Nov 10 14:38:39 2022 -0800 gprofng: fix typo in configure.ac gprofng/ChangeLog 2022-11-10 Vladimir Mezentsev <vladimir.mezentsev@oracle.com> * configure.ac: Fix typo in redirect operator. * configure: Rebuild. Diff: --- gprofng/configure | 2 +- gprofng/configure.ac | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/gprofng/configure b/gprofng/configure index c90e36cb1cf..8ad5ebd67be 100755 --- a/gprofng/configure +++ b/gprofng/configure @@ -16572,7 +16572,7 @@ class Simple{ } } EOF - if { ac_try='$JAVAC configtest.java &5 2>&1' + if { ac_try='$JAVAC configtest.java >&5 2>&5' { { eval echo "\"\$as_me\":${as_lineno-$LINENO}: \"$ac_try\""; } >&5 (eval $ac_try) 2>&5 ac_status=$? diff --git a/gprofng/configure.ac b/gprofng/configure.ac index 2d7640dfdc8..bbad953cf4f 100644 --- a/gprofng/configure.ac +++ b/gprofng/configure.ac @@ -142,7 +142,7 @@ class Simple{ } } EOF - if AC_TRY_COMMAND($JAVAC configtest.java &AS_MESSAGE_LOG_FD 2>&1); then + if AC_TRY_COMMAND($JAVAC configtest.java >&AS_MESSAGE_LOG_FD 2>&AS_MESSAGE_LOG_FD); then GPROFNG_BROKEN_JAVAC=no else GPROFNG_BROKEN_JAVAC=yes
reply other threads:[~2022-11-11 1:25 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=20221111012546.BF14C3858D1E@sourceware.org \ --to=vmezents@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: linkBe 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).