From: Steve Ellcey <sje@cup.hp.com>
To: gdb@sourceware.org
Subject: mmalloc question
Date: Thu, 30 Jun 2005 14:39:00 -0000 [thread overview]
Message-ID: <200506301438.HAA20132@hpsje.cup.hp.com> (raw)
I have been looking at removing the uses of BFD_NEED_DECLARATION from
the source tree and replacing it with the standard AC_CHECK_DECL. This
is possible now that we have moved up from autoconf 2.14. Eventually, I
would like to remove the definition of BFD_NEED_DECLARATION from the
src/bfd subdirectory.
gdb uses BFD_NEED_DECLARATION in two subdirectories, in src/gdb, which
should be easy to fix and in src/mmalloc. Now mmalloc says it is no
longer maintained and it hasn't been updated since 2003. My question
is: does mmalloc need to be updated if I want to get rid of
BFD_NEED_DECLARATION or can it be left alone with the knowledge that
after the BFD_NEED_DECLARATION definition is removed from the src/bfd it
will no longer build? The top-level configure still seems to allow for
mmalloc to be built, but when I ran 'make all-mmalloc' it didn't
actually try to build anything, it just returned after doing nothing.
Steve Ellcey
sje@cup.hp.com
next reply other threads:[~2005-06-30 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 14:39 Steve Ellcey [this message]
2005-06-30 21:46 ` Mark Kettenis
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=200506301438.HAA20132@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=gdb@sourceware.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