From: Mark Kettenis <kettenis@chello.nl>
To: gdb@sources.redhat.com
Subject: [RFC] Shared library cruft in configure.in
Date: Thu, 02 Jan 2003 21:02:00 -0000 [thread overview]
Message-ID: <200301022102.h02L2JnG061454@elgar.kettenis.dyndns.org> (raw)
There is some code in configure.in to "support" --enable-shared. Its
purpose seems to be to make it possible to build a GDB that's linked
against shared versions of libraries from elsewhere in the Cygnus tree
(e.g. bfd, opcodes). However, we always use static libraries when
linking (../bfd/libbfd.a, ../opcodes/opcodes.a). Therefore I think
the code is completely useless, and I propose to whack it. If, in the
future, we want to support a GDB linked against a shared libbfd and
libopcodes, we shouldn't use this code anyway, but use libtool
instead.
Any objects?
Mark
next reply other threads:[~2003-01-02 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 21:02 Mark Kettenis [this message]
2003-01-02 22:23 ` Daniel Jacobowitz
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=200301022102.h02L2JnG061454@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=gdb@sources.redhat.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