From: amodra@one.net.au
To: LaMont Jones <lamont@hp.com>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Re: still getting $$dyncall refs in shlibs
Date: Fri, 25 May 2001 08:32:02 +0930 [thread overview]
Message-ID: <20010525083202.E9275@squeak.one.net.au> (raw)
In-Reply-To: <20010524215930.76E741872C@security.hp.com>; from lamont@hp.com on Thu, May 24, 2001 at 03:59:30PM -0600
On Thu, May 24, 2001 at 03:59:30PM -0600, LaMont Jones wrote:
> > 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:
Too much can go wrong building shared libs just using ld. It's far
better to build using gcc -shared. In this case, the problem is that
the shlib needs to be built linked against libgcc to satisfy the
millicode reference.
Alan
next prev parent reply other threads:[~2001-05-24 22:55 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 ` [parisc-linux] " LaMont Jones
2001-05-24 23:02 ` amodra [this message]
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=20010525083202.E9275@squeak.one.net.au \
--to=amodra@one.net.au \
--cc=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 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.