public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
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 04:54:00 -0000	[thread overview]
Message-ID: <u8lmcrfj88.fsf@gromit.moeb> (raw)
In-Reply-To: <u8pu23fkk3.fsf@gromit.moeb> (Andreas Jaeger's message of "Sun, 17 Mar 2002 13:25:16 +0100")

Andreas Jaeger <aj@suse.de> writes:

[...]

> So, how can we fix that configure test - and do we need to add -lgcc_s
> for sln?

Not -lgcc_s, it's -lgcc_eh.

I still don't understand why it fails on my newer system but works
fine on an older system...

This seems to be related to this patch:

2001-12-15  Jakub Jelinek  <jakub@redhat.com>
        [...]
        * gcc.c (init_gcc_specs): For -static-libgcc, use -lgcc -lgcc_eh.
        If neither -static-libgcc nor -shared-libgcc is passed and -shared,
        use -lgcc if LINK_EH_SPEC is defined and -lgcc_s -lgcc if not.
        If none of the above switches are passed, use -lgcc -lgcc_eh.
        (init_spec): If LINK_EH_SPEC is defined, prepend it to link_spec.

Jakub, can you have a look at glibc?  Any ideas what's broken - or
what I'm doing wrong on my system?

Thanks,
Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

  reply	other threads:[~2002-03-17 12:54 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 [this message]
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=u8lmcrfj88.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).