From: Jakub Jelinek <jakub@redhat.com>
To: Andreas Jaeger <aj@suse.de>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: dwarf2 unwind info check broken
Date: Sun, 24 Mar 2002 11:02:00 -0000 [thread overview]
Message-ID: <20020324200155.S32482@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <u8g02pyiqc.fsf@gromit.moeb>; from aj@suse.de on Sun, Mar 24, 2002 at 06:32:27PM +0100
On Sun, Mar 24, 2002 at 06:32:27PM +0100, Andreas Jaeger wrote:
> Andreas Jaeger <aj@suse.de> writes:
>
> > Jakub Jelinek <jakub@redhat.com> writes:
> >
> >> So the unwind info check should be extended to something like
> >> (untested):
> >
> > I've tested this now extensivly and I'm happy with the appended
> > version of this patch.
>
> I missed one point in my testing: Building of static programs in
> glibc:
>
> /opt/gcc/3.1-devel/bin/gcc -nostdlib -nostartfiles -static -o /builds/glibc/gcc-3.1/elf/sln /builds/glibc/gcc-3.1/csu/crt1.o /builds/glibc/gcc-3.1/csu/crti.o `/opt/gcc/3.1-devel/bin/gcc --print-file-name=crtbegin.o` /builds/glibc/gcc-3.1/elf/sln.o /builds/glibc/gcc-3.1/libc.a -lgcc /builds/glibc/gcc-3.1/libc.a `/opt/gcc/3.1-devel/bin/gcc --print-file-name=crtend.o` /builds/glibc/gcc-3.1/csu/crtn.o
> /opt/gcc/3.1-devel/lib/gcc-lib/i686-pc-linux-gnu/3.1/crtbegin.o: In function `__do_global_dtors_aux':
> /opt/gcc/3.1-devel/lib/gcc-lib/i686-pc-linux-gnu/3.1/crtbegin.o(.text+0x36): undefined reference to `__deregister_frame_info_bases'
> ...
>
> We use -static but since we use -nostdlib, -lgcc_eh is not added
> here:-(
Configure should detect if -lgcc_eh exist and add it in in addition to
-lgcc (well, for gcc-3.1+ configured with binutils 2.12 it doesn't matter),
but for gcc-3.1+ configured with older binutils it matters.
Jakub
next prev parent reply other threads:[~2002-03-24 19:02 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
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 [this message]
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=20020324200155.S32482@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=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).