From: walt <wa1ter@myrealbox.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH] to make grub2 compile on NetBSD
Date: Mon, 04 Feb 2008 14:55:34 -0800 [thread overview]
Message-ID: <fo853p$es5$1@ger.gmane.org> (raw)
In-Reply-To: <20080204222712.GA28299@thorin>
Robert Millan 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.
>> Second try:
>>
>> Make NetBSD's gcc happy.
>>
>> * kern/mm.c: New dummy symbol __enable_execute_stack.
>> (include/grub/mm.h): Likewise.
>
> This ChangeLog entry seems wrong. I'll write it up for you, as it's easier to
> explain with an example:
>
> Make NetBSD's gcc happy.
>
> * include/grub/mm.h
> [__NetBSD__] (__enable_execute_stack): New function prototype.
> * kern/mm.c
> [__NetBSD__] (__enable_execute_stack): New function.
Okay, thanks. Does the [__NetBSD__] token denote an #ifdef? How
would I indicate a patch for, say, Net/Free/Dragonfly BSD's at the
same time?
Oh, and should you mention that the new function does nothing?
Marco: I didn't add the header for the changelog because I don't
know who (if anyone) is going to commit it.
next prev parent reply other threads:[~2008-02-04 22:55 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 [this message]
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
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='fo853p$es5$1@ger.gmane.org' \
--to=wa1ter@myrealbox.com \
--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.