From: Andreas Jaeger <aj@suse.de>
To: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: dwarf2 unwind info check broken
Date: Sun, 17 Mar 2002 02:19:00 -0000 [thread overview]
Message-ID: <u8d6y3h4y7.fsf@gromit.moeb> (raw)
In-Reply-To: <u8henfh58z.fsf@gromit.moeb> (Andreas Jaeger's message of "Sun, 17 Mar 2002 11:13:00 +0100")
Andreas Jaeger <aj@suse.de> writes:
> With current binutils and both gcc 2.95.3 and GCC 3.2 CVS on
> i686-linux-gnu I now get:
>
> checking for DWARF2 unwind info support... (cached) no
>
> The test program from configure:
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> static char __EH_FRAME_BEGIN__[];
I figured out the problem: the []; gets removed by autoconf - but my
autoconf version didn't remove it. :-(
We should remove the [] from configure.in since it's broken there.
Ok to commit the appended patch?
Andreas
2002-03-17 Andreas Jaeger <aj@suse.de>
* configure.in: Fix dwarf2 unwind test.
============================================================
Index: configure.in
--- configure.in 2002/03/16 02:54:00 1.340
+++ configure.in 2002/03/17 10:19:06
@@ -1389,7 +1389,7 @@ fi
AC_CACHE_CHECK(for DWARF2 unwind info support, libc_cv_gcc_dwarf2_unwind_info,
[cat > conftest.c <<EOF
#line __oline__ "configure"
-static char __EH_FRAME_BEGIN__[];
+static char __EH_FRAME_BEGIN__;
_start ()
{
#ifdef CHECK__register_frame
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2002-03-17 10:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-17 2:14 Andreas Jaeger
2002-03-17 2:19 ` Andreas Jaeger [this message]
2002-03-17 4:25 ` Andreas Jaeger
2002-03-17 4:54 ` Andreas Jaeger
2002-03-17 12:14 ` Jakub Jelinek
2002-03-19 8:32 ` Andreas Jaeger
2002-03-19 12:19 ` Andreas Jaeger
[not found] ` <20020319160357.J1213@devserv.devel.redhat.com>
2002-03-19 13:25 ` Andreas Jaeger
2002-03-24 8:32 ` Andreas Jaeger
2002-03-24 9:34 ` Andreas Jaeger
2002-03-24 11:02 ` Jakub Jelinek
2002-03-24 11:48 ` Andreas Jaeger
2002-03-24 12:38 ` Jakub Jelinek
2002-03-25 22:30 ` Andreas Jaeger
2002-03-17 7:02 ` Andreas Schwab
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=u8d6y3h4y7.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=libc-hacker@sources.redhat.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).