From: Helge Deller <deller@gmx.de>
To: carlos@baldric.uwo.ca (Carlos O'Donell)
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] strange GNU ld / libgcc_s.so problems
Date: Mon, 15 Dec 2003 21:42:21 +0100 [thread overview]
Message-ID: <200312152142.21505.deller@gmx.de> (raw)
In-Reply-To: <200312142312.hBENCSHO002332@hiauly1.hia.nrc.ca>
On Monday 15 December 2003 00:12, John David Anglin wrote:
> > > -lgcc_s (//usr/lib/libstdc++.so: undefined reference to `_Unwind_SjLj_Resume@GCC_3.0'
> > > /usr/lib/libstdc++.so: undefined reference to `_Unwind_SjLj_Register@GCC_3.0'
> > > /usr/lib/libstdc++.so: undefined reference to `_Unwind_SjLj_RaiseException@GCC_3.0'
> > > /usr/lib/libstdc++.so: undefined reference to `_Unwind_SjLj_Unregister@GCC_3.0'
> > > /usr/lib/libstdc++.so: undefined reference to `_Unwind_SjLj_Resume_or_Rethrow@GCC_3.3'
> > > usr/lib/libgcc_s.so)
>
> Debian builds GCC using sjlj exceptions. This can happen if you use
> GCC built using dwarf2 exception support (the default).
Hi Dave,
I'm only using debian's official binaries thru "apt-get update" - including gcc/g++:
c3000:/var/cache/apt/archives# dpkg -l | grep gcc
ii gcc 3.3.1-2 The GNU C compiler.
pi gcc-3.2-base 3.2.3-8 The GNU Compiler Collection (base package)
ii gcc-3.3 3.3.2-4 The GNU C compiler
ii gcc-3.3-base 3.3.2-4 The GNU Compiler Collection (base package)
ii gcc-hppa64 3.0-0pre010427 Cross gcc for hppa64
ii libgcc1 3.3.2-4 GCC support library
next prev parent reply other threads:[~2003-12-15 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-14 11:11 [parisc-linux] strange GNU ld / libgcc_s.so problems Helge Deller
2003-12-14 22:16 ` Carlos O'Donell
2003-12-14 23:12 ` John David Anglin
2003-12-15 20:42 ` Helge Deller [this message]
2003-12-15 20:46 ` Helge Deller
2003-12-15 21:05 ` John David Anglin
2003-12-15 21:38 ` Helge Deller
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=200312152142.21505.deller@gmx.de \
--to=deller@gmx.de \
--cc=carlos@baldric.uwo.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.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