From: "Yoshinori K. Okuji" <okuji@gnu.org>
To: Hollis Blanchard <hollis@penguinppc.org>
Cc: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: --enable-mm-debug breakage
Date: Wed, 26 Apr 2006 10:47:21 +0200 [thread overview]
Message-ID: <200604261047.21806.okuji@gnu.org> (raw)
In-Reply-To: <2b1a8b979a9e3455b8ff38c6fe24d2de@penguinppc.org>
On Wednesday 26 April 2006 02:10, Hollis Blanchard wrote:
> On Apr 25, 2006, at 3:08 PM, Yoshinori K. Okuji wrote:
> > Also, this change adds an
> > intensive debugging feature for the memory manager via the
> > configure option "--enable-mm-debug".
>
> I fixed the breakage from renaming "abort".
Thank you.
> However, the build is now broken when not using --enable-mm-debug:
> grubof_symlist.c: In function 'grub_register_exported_symbols':
> grubof_symlist.c:134: error: 'grub_debug_malloc' undeclared (first use
> in this function)
>
> Given gensymlist.sh, I can see two ways to solve this problem:
> 1) Provide empty stubs for those debug functions.
> 2) Use the regular debugging infrastructure, as I mentioned before.
> That is what is was designed for, so it seems to be the obvious
> solution. grub_mm_debug(), which has no callers, is the only function
> that won't fit.
>
No, this problem happens only because grubof_symlist.c is not regenerated when
you rerun configure. That is, this is a dependency problem in the Makefile.
Okuji
next prev parent reply other threads:[~2006-04-26 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1FYTpn-0003L4-RP@savannah.gnu.org>
2006-04-25 23:22 ` grub_machine_set_prefix, --enable-mm-debug Hollis Blanchard
2006-04-26 8:49 ` Yoshinori K. Okuji
2006-04-26 8:57 ` Marco Gerards
2006-04-26 9:22 ` Yoshinori K. Okuji
2006-04-26 10:00 ` Marco Gerards
2006-04-26 10:45 ` Yoshinori K. Okuji
2006-04-26 0:10 ` --enable-mm-debug breakage Hollis Blanchard
2006-04-26 2:06 ` Hollis Blanchard
2006-04-26 8:47 ` Yoshinori K. Okuji [this message]
2006-04-26 19:31 ` Yoshinori K. Okuji
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=200604261047.21806.okuji@gnu.org \
--to=okuji@gnu.org \
--cc=grub-devel@gnu.org \
--cc=hollis@penguinppc.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.