From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: libc-alpha@sourceware.org
Cc: Joseph Myers <joseph@codesourcery.com>,
Paul Pluzhnikov <ppluzhnikov@google.com>
Subject: [COMMITTED] Regenerate configure fragment -- BZ 25337.
Date: Tue, 23 May 2023 16:26:42 +0000 [thread overview]
Message-ID: <20230523162641.412294-1-ppluzhnikov@google.com> (raw)
In-Reply-To: <df167943-10d0-7f24-d656-3745cb23d686@codesourcery.com>
In commit 0b25c28e028b63c95108c442d8112811107e4c13 I updated congure.ac
but neglected to regenerate updated configure.
Fix this here.
---
sysdeps/powerpc/powerpc64/configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sysdeps/powerpc/powerpc64/configure b/sysdeps/powerpc/powerpc64/configure
index f57c58ac11..e09052a339 100644
--- a/sysdeps/powerpc/powerpc64/configure
+++ b/sysdeps/powerpc/powerpc64/configure
@@ -38,7 +38,7 @@ fi
# We check if compiler supports @notoc generation since there is no
# gain by enabling it if it will be optimized away by the linker.
# It also helps linkers that might not optimize it and end up
-# generating stubs with ISA 3.1 instruction even targetting older ISA.
+# generating stubs with ISA 3.1 instruction even targeting older ISA.
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking if the compiler supports @notoc" >&5
$as_echo_n "checking if the compiler supports @notoc... " >&6; }
if ${libc_cv_ppc64_notoc+:} false; then :
--
2.40.1.698.g37aff9b760-goog
prev parent reply other threads:[~2023-05-23 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 12:15 [PATCH] Fix misspellings in sysdeps/powerpc " Paul Pluzhnikov
2023-05-23 15:14 ` Rajalakshmi Srinivasaraghavan
2023-05-23 15:43 ` Joseph Myers
2023-05-23 16:26 ` Paul Pluzhnikov [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=20230523162641.412294-1-ppluzhnikov@google.com \
--to=ppluzhnikov@google.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@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).