From: LaMont Jones <lamont@hp.com>
To: LaMont Jones <lamont@hp.com>
Cc: parisc-linux@parisc-linux.org, lamont@hp.com
Subject: [parisc-linux] Re: still getting $$dyncall refs in shlibs
Date: Thu, 24 May 2001 15:59:30 -0600 [thread overview]
Message-ID: <20010524215930.76E741872C@security.hp.com> (raw)
In-Reply-To: Your message of "Thu, 24 May 2001 15:32:59 MDT." <20010524213301.126241872C@security.hp.com>
> With the new toolchain, sipp still builds a libsipp.so.3.1 trips the
> bug checker. Checking everything on the system doesn't find any bad
> libs. Here is the build output for libsipp.so:
Add the following .debs to the list of things that still build borken:
auto-apt_0.3.11.0.1_hppa.deb
installwatch_0.5.5-3.0.1_hppa.deb
libc-client2000_2000cdebian-2_hppa.deb
libg20_0.42.20010417-1.0.1_hppa.deb
libmagick++5_5.3.3-5_hppa.deb
libmimelib1_2.1.0-1.0.1_hppa.deb
libpam-radius-auth_1.3.11-3.0.1_hppa.deb
libseal1_1.07-4.0.1_hppa.deb
sciplot1_1.36-8.0.1_hppa.deb
sipp_3.1-7.0.1_hppa.deb
slatec_4.1-4.0.1_hppa.deb
lamont
next prev parent reply other threads:[~2001-05-24 22:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 21:32 [parisc-linux] still getting $$dyncall refs in shlibs LaMont Jones
2001-05-24 21:42 ` Matthew Wilcox
2001-05-24 21:59 ` LaMont Jones [this message]
2001-05-24 23:02 ` [parisc-linux] " amodra
2001-05-24 22:59 ` John David Anglin
2001-05-24 23:14 ` LaMont Jones
2001-05-24 23:26 ` 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=20010524215930.76E741872C@security.hp.com \
--to=lamont@hp.com \
--cc=parisc-linux@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