public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Paul Pluzhnikov <ppluzhnikov@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] Regenerate configure fragment -- BZ 25337.
Date: Tue, 23 May 2023 16:24:05 +0000 (GMT)	[thread overview]
Message-ID: <20230523162405.942743858D35@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=6b3ddc9ae57763b188fec63da7740b7ab2ec6edb

commit 6b3ddc9ae57763b188fec63da7740b7ab2ec6edb
Author: Paul Pluzhnikov <ppluzhnikov@google.com>
Date:   Tue May 23 16:21:29 2023 +0000

    Regenerate configure fragment -- BZ 25337.
    
    In commit 0b25c28e028b63c95108c442d8112811107e4c13 I updated congure.ac
    but neglected to regenerate updated configure.
    
    Fix this here.

Diff:
---
 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 :

                 reply	other threads:[~2023-05-23 16:24 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=20230523162405.942743858D35@sourceware.org \
    --to=ppluzhnikov@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).