All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Carlos O'Donell <carlos@baldric.uwo.ca>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] strange GNU ld / libgcc_s.so problems
Date: Mon, 15 Dec 2003 21:46:44 +0100	[thread overview]
Message-ID: <200312152146.44613.deller@gmx.de> (raw)
In-Reply-To: <20031214221629.GZ13882@systemhalted>

On Sunday 14 December 2003 23:16, Carlos O'Donell wrote:
> On Sun, Dec 14, 2003 at 12:11:07PM +0100, Helge Deller wrote:
> > Below is the output and I don't understand the part which I marked with "######".
> > Why does collect2 suddenly tries to resolve libstdc++.so while it searched for 
> > libgcc_s.so ? All other libraries (e.g.-lutil) behave IMHO normal.
> > Any ideas ? This seems to me like a bug in gcc 3.3.2, but I'm no expert here.
> > 
> ... SNIP ...
> 
> > attempt to open /usr/X11R6/lib/libgcc_s.so failed
> > attempt to open /usr/X11R6/lib/libgcc_s.a failed
> > attempt to open /opt/kde/qt/lib/libgcc_s.so failed
> > attempt to open /opt/kde/qt/lib/libgcc_s.a failed
> > attempt to open /opt/kde/lib/libgcc_s.so failed
> > attempt to open /opt/kde/lib/libgcc_s.a failed
> > attempt to open /usr/lib/libgcc_s.so succeeded
> > -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)
> > 
> > ##### ^^^ Why does /usr/lib/libstdc++.so comes into the game here ?
> > ##### The double "//" seems suspect too, since it continues with "usr/lib/libgcc_s.so" 
> > ##### in the last line without the trailing "/". It seems this "string" was broken up
> > ##### right in the middle....
> 
> Where did that file come from? Is this a debian box?
> You should have:
> 
> /usr/lib/gcc-lib/hppa-linux/<gcc-version>/libgcc_s.so
> pointing to /lib/libgcc_s.so

Yes - Debian box and correct symlink.

> I suggest you try building this in a clean unstable chroot :)

:-)

Thanks,
Helge

  parent reply	other threads:[~2003-12-15 20:47 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
2003-12-15 20:46   ` Helge Deller [this message]
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=200312152146.44613.deller@gmx.de \
    --to=deller@gmx.de \
    --cc=carlos@baldric.uwo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.