public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paulo Matos <paulo@matos-sorge.com>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] Fix typo
Date: Sun, 10 May 2015 21:01:00 -0000	[thread overview]
Message-ID: <miogtv$dk$1@ger.gmane.org> (raw)

OK to commit?

    2015-05-10  Paulo Matos  <paulo@matos-sorge.com>  
      
        * configure.ac: Fix typo.  
        * configure: Regenerate.  
  
diff --git a/configure b/configure  
index a3f66ba..8ee279f 100755  
--- a/configure  
+++ b/configure  
@@ -7423,7 +7423,7 @@ fi  
 # multilib is not explicitly enabled.  
 case "$target:$have_compiler:$host:$target:$enable_multilib" in  
   x86_64-*linux*:yes:$build:$build:)  
-    # Make sure we have a developement environment that handles 32-bit  
+    # Make sure we have a development environment that handles 32-bit  
     dev64=no  
     echo "int main () { return 0; }" > conftest.c  
     ${CC} -m32 -o conftest ${CFLAGS} ${CPPFLAGS} ${LDFLAGS} conftest.c  
@@ -7434,7 +7434,7 @@ case "$target:$have_compiler:$host:$target:
$enable_multilib" in  
     fi  
     rm -f conftest*  
     if test x${dev64} != xyes ; then  
-      as_fn_error "I suspect your system does not have 32-bit 
developement libraries (libc and headers). If you have them, rerun 
configure with --enable-multilib. If you do not have them, and want to 
build a 64-bit-only compiler, rerun configure with --disable-multilib." 
"$LINENO" 5
+      as_fn_error "I suspect your system does not have 32-bit 
development libraries (libc and headers). If you have them, rerun 
configure with --enable-multilib. If you do not have them, and want to 
build a 64-bit-only compiler, rerun configure with --disable-multilib." 
"$LINENO" 5
     fi
     ;;
 esac
diff --git a/configure.ac b/configure.ac
index 987dfab..4081fb9 100644
--- a/configure.ac
+++ b/configure.ac
@@ -3063,7 +3063,7 @@ fi
 # multilib is not explicitly enabled.
 case "$target:$have_compiler:$host:$target:$enable_multilib" in
   x86_64-*linux*:yes:$build:$build:)
-    # Make sure we have a developement environment that handles 32-bit
+    # Make sure we have a development environment that handles 32-bit
     dev64=no
     echo "int main () { return 0; }" > conftest.c
     ${CC} -m32 -o conftest ${CFLAGS} ${CPPFLAGS} ${LDFLAGS} conftest.c
@@ -3074,7 +3074,7 @@ case "$target:$have_compiler:$host:$target:
$enable_multilib" in
     fi 
     rm -f conftest*
     if test x${dev64} != xyes ; then
-      AC_MSG_ERROR([I suspect your system does not have 32-bit 
developement libraries (libc and headers). If you have them, rerun 
configure with --enable-multilib. If you do not have them, and want to 
build a 64-bit-only compiler, rerun configure with --disable-multilib.])
+      AC_MSG_ERROR([I suspect your system does not have 32-bit 
development libraries (libc and headers). If you have them, rerun 
configure with --enable-multilib. If you do not have them, and want to 
build a 64-bit-only compiler, rerun configure with --disable-multilib.])
     fi
     ;;
 esac


             reply	other threads:[~2015-05-10 21:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-10 21:01 Paulo Matos [this message]
2015-05-11  4:07 ` Jeff Law
2015-05-11 18:15   ` Paulo Matos
2015-11-03 14:16 Yulia Koval
2015-11-03 14:32 ` Uros Bizjak
2015-11-03 16:04   ` Yulia Koval
2019-10-24 11:20 Richard Biener
2022-06-23  3:01 Xionghu Luo

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='miogtv$dk$1@ger.gmane.org' \
    --to=paulo@matos-sorge.com \
    --cc=gcc-patches@gcc.gnu.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).