From: "H . J . Lu" <hjl@lucon.org>
To: John Reiser <jreiser@BitWagon.com>
Cc: binutils@sources.redhat.com
Subject: Re: bfd.flags&DYNAMIC vs. bfd_link_info.static
Date: Fri, 01 Jun 2001 13:21:00 -0000 [thread overview]
Message-ID: <20010601132102.B8818@lucon.org> (raw)
In-Reply-To: <3B17F612.7DACA4C2@BitWagon.com>
On Fri, Jun 01, 2001 at 01:07:46PM -0700, John Reiser wrote:
> > Please also CC your binutils bug reports to binutils@sources.redhat.com.
> > There are no archives for bug-binutils.
>
> OK. I note that Philip Blundell has provided a reference in this case.
I don't see anything wrong. You have to used -shared to create DSO.
H.J.
next prev parent reply other threads:[~2001-06-01 13:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <991410192.21718.ezmlm@sources.redhat.com>
2001-06-01 11:35 ` John Reiser
2001-06-01 12:08 ` H . J . Lu
2001-06-01 13:02 ` Philip Blundell
2001-06-01 13:09 ` H . J . Lu
2001-06-01 13:15 ` John Reiser
2001-06-01 13:21 ` H . J . Lu [this message]
2001-06-01 13:43 ` John Reiser
2001-06-01 15:38 ` John Reiser
2001-06-02 7:06 ` Alan Modra
2001-06-04 22:38 ` elf32-i386.c .got Alan Modra
2001-06-05 11:45 ` John Reiser
2001-06-01 13:34 ` bfd.flags&DYNAMIC vs. bfd_link_info.static Philip Blundell
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=20010601132102.B8818@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--cc=jreiser@BitWagon.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).