From: LaMont Jones <lamont@hp.com>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: amodra@one.net.au, lamont@hp.com, parisc-linux@parisc-linux.org,
lamont@hp.com
Subject: Re: [parisc-linux] Re: still getting $$dyncall refs in shlibs
Date: Thu, 24 May 2001 17:14:17 -0600 [thread overview]
Message-ID: <20010524231417.584391872C@security.hp.com> (raw)
In-Reply-To: Your message of "Thu, 24 May 2001 18:59:17 EDT." <200105242259.SAA02789@hiauly1.hia.nrc.ca>
> That also applies to libtool which uses `ld' directly. Gcc will run
> collect2 if needed. This is necessary for correctly processing
> constructors and destructors.
Will someone file the defect against libtool, please?
lamont
next prev parent reply other threads:[~2001-05-24 23:14 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
2001-05-24 22:59 ` John David Anglin
2001-05-24 23:14 ` LaMont Jones [this message]
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=20010524231417.584391872C@security.hp.com \
--to=lamont@hp.com \
--cc=amodra@one.net.au \
--cc=dave@hiauly1.hia.nrc.ca \
--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