From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] We need our own libgcc-compat for a leaked __clz_tab
Date: Wed, 29 Jan 2003 00:43:31 -0500 [thread overview]
Message-ID: <20030129054331.GF9855@systemhalted> (raw)
PA,
Problem:
- GCC used to export a symbol for __clz_tab (GLOBAL DEFAULT)
- Everything in debian is being built with newer tools (GCC 3.2).
- Symbol is no longer leaked (LOCAL HIDDEN)
- Libraries that had the leadked symbol are rebuilt (e.g. libcrypto)
- Binaries that had relocations against the symbol are failing (e.g.
wget)
Solution:
- Create a libgcc-compat in glibc for the symbol __clz_tab
= Various arches have them for certain symbols that were leaked
= from GCC when we the GNU tools didn't have ".hidden"
= So examples exist...
- Test the solution to see that atleast "wget" works.
- Put it into Debians glibc as a dpatch.
- Submit upstream for fame and glory.
I'm writing a paper and doing research until Saturday.
If someone feels gutsy enough to attempt a fix, please have at it...
If not, it's currently the highest priority item on my TODO.
Cheers,
Carlos.
next reply other threads:[~2003-01-29 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 5:43 Carlos O'Donell [this message]
2003-01-29 16:50 ` [parisc-linux] We need our own libgcc-compat for a leaked __clz_tab John David Anglin
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=20030129054331.GF9855@systemhalted \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox