From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Cc: Roger Sayle <roger@nextmovesoftware.com>
Subject: [PATCH (pushed)] build: regenerate gcc/configure
Date: Thu, 18 Aug 2022 12:40:46 +0200 [thread overview]
Message-ID: <81c3a88a-024f-ed4b-1d37-238fae3326c5@suse.cz> (raw)
After the change 71f068a9b3332a2179dfc807cf9138f691d77461, gcc/configure
needs to re-generated.
gcc/ChangeLog:
* configure: Regenerate.
---
gcc/configure | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/gcc/configure b/gcc/configure
index 05efa5b01ef..da7a45066b5 100755
--- a/gcc/configure
+++ b/gcc/configure
@@ -5226,12 +5226,16 @@ else
GNATMAKE="$ac_cv_prog_GNATMAKE"
fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether compiler driver understands Ada" >&5
-$as_echo_n "checking whether compiler driver understands Ada... " >&6; }
+{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether compiler driver understands Ada and is recent enough" >&5
+$as_echo_n "checking whether compiler driver understands Ada and is recent enough... " >&6; }
if ${acx_cv_cc_gcc_supports_ada+:} false; then :
$as_echo_n "(cached) " >&6
else
cat >conftest.adb <<EOF
+pragma Warnings (Off);
+with System.CRTL;
+pragma Warnings (On);
+use type System.CRTL.int64;
procedure conftest is begin null; end conftest;
EOF
acx_cv_cc_gcc_supports_ada=no
@@ -19674,7 +19678,7 @@ else
lt_dlunknown=0; lt_dlno_uscore=1; lt_dlneed_uscore=2
lt_status=$lt_dlunknown
cat > conftest.$ac_ext <<_LT_EOF
-#line 19677 "configure"
+#line 19681 "configure"
#include "confdefs.h"
#if HAVE_DLFCN_H
@@ -19780,7 +19784,7 @@ else
lt_dlunknown=0; lt_dlno_uscore=1; lt_dlneed_uscore=2
lt_status=$lt_dlunknown
cat > conftest.$ac_ext <<_LT_EOF
-#line 19783 "configure"
+#line 19787 "configure"
#include "confdefs.h"
#if HAVE_DLFCN_H
--
2.37.1
reply other threads:[~2022-08-18 10:40 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=81c3a88a-024f-ed4b-1d37-238fae3326c5@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=roger@nextmovesoftware.com \
/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).