From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] to make grub2 compile on NetBSD
Date: Tue, 12 Feb 2008 08:22:11 +0100 [thread overview]
Message-ID: <200802120822.11993.okuji@enbug.org> (raw)
In-Reply-To: <foqj2o$c28$1@ger.gmane.org>
On Monday 11 February 2008 23:44, walt wrote:
> On Mon, 2008-02-04 at 16:56 +0100, Marco Gerards wrote:
> > walt <wa1ter@myrealbox.com> writes:
> > > NetBSD's gcc wants libgcc and libc to define __enable_execute_stack,
> > > but this is useless for a free-standing executable like grub. Define
> > > a dummy function in lieu of libgcc to supply __enable_execute_stack.
> >
> > ... If this is for NetBSD only,
> > shouldn't you add a #ifdef instead of a comment?
>
> Third try:
>
> 2008-??-?? walt <wa1ter@myrealbox.com>
>
> Make NetBSD's gcc happy. Based on pkgsrc/wip/grub2 patches.
>
> * include/grub/mm.h
> [__NetBSD__] (__enable_execute_stack): New function prototype.
> * kern/mm.c
> [__NetBSD__] (__enable_execute_stack): New function.
I don't strongly object to this way, but I feel that it would be better to
probe if __enable_execute_stack must be defined, and define a variable in
configure, instead of hardcoding __NetBSD__.
Okuji
next prev parent reply other threads:[~2008-02-12 7:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 21:33 [PATCH] to make grub2 compile on NetBSD walt
2008-02-04 15:56 ` Marco Gerards
2008-02-04 20:21 ` walt
2008-02-04 20:55 ` Marco Gerards
2008-02-04 22:27 ` Robert Millan
2008-02-04 22:55 ` walt
2008-02-04 23:30 ` Robert Millan
2008-02-05 6:37 ` Marco Gerards
2008-02-11 22:44 ` walt
2008-02-12 7:22 ` Yoshinori K. Okuji [this message]
2008-02-12 23:56 ` walt
2008-02-13 3:55 ` 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=200802120822.11993.okuji@enbug.org \
--to=okuji@enbug.org \
--cc=grub-devel@gnu.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.