From: sc843@bard.edu
To: ultralinux@vger.kernel.org
Subject: Re: libstdc++ bus errors
Date: Wed, 14 Nov 2001 17:15:59 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-100575809507289@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-100562646118090@msgid-missing>
> > Upgrading binutils to 2.11.2 doesn't solve the problem, because ld.so
> > doesn't understand R_SPARC_UA32 relocations...
> Upgrade glibc, then binutils :-) Current glibc understands
> the UA32 relocs properly.
I don't think this is the sole cause of the problem. I have glibc 2.2.4, which
(according to my hand-checking) includes the fix for R_SPARC_UA32
mentioned in an earlier message:
> Ah yes, I found the requisite patch... thanks.
> http://sources.redhat.com/ml/libc-alpha/2001-07/msg00021.html
...but still C++ programs have bus errors.
Perhaps a related issue could be that I overrode the default behavior of
the 32->64 cross compiler to copy all the system headers into
$PREFIX/sparc64-linux/sys-includes
and instead symlinked that directory to
$PREFIX/include
I don't know what else the problem might be. Must I upgrade to a CVS
version of binutils? (I have 2.11)
Would it help if I build gdb and tried to figure out the source of the error
more precisely, or is this well-known?
Sincerely,
Sean Callanan
prev parent reply other threads:[~2001-11-14 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 4:39 libstdc++ bus errors Sean Callanan
2001-11-13 5:20 ` Jeff Sturm
2001-11-13 5:33 ` David S. Miller
2001-11-13 6:00 ` Jeff Sturm
2001-11-14 17:15 ` sc843 [this message]
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=marc-linux-ultrasparc-100575809507289@msgid-missing \
--to=sc843@bard.edu \
--cc=ultralinux@vger.kernel.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