From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Compiling grub2 on *BSD?
Date: Wed, 30 Jan 2008 20:14:50 +0100 [thread overview]
Message-ID: <20080130191450.GA1393@thorin> (raw)
In-Reply-To: <1201720010.27623.26.camel@k9.localnet>
On Wed, Jan 30, 2008 at 11:06:50AM -0800, walt wrote:
>
> > Anyway, your suggestion helps, but not quite enough. The c code now
> > compiles and links okay into *.mod files, but now __enable_execute_stack
> > shows up in several und-*.lst files...
>
> I've been hacking the various flags for elf.mod just to get *any* module
> to link properly but no luck. Here is the actual text printed by gcc
> as it links elf.mod:
You don't need any of that. Just make __enable_execute_stack appear in
def-kernel.lst.
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-01-30 19:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 17:08 Compiling grub2 on *BSD? walt
2008-01-26 17:21 ` Robert Millan
2008-01-26 18:15 ` Bean
2008-01-28 10:14 ` Bean
2008-01-28 10:47 ` Robert Millan
2008-01-28 11:15 ` Bean
2008-01-28 12:56 ` Marco Gerards
2008-01-29 11:00 ` Bean
2008-01-26 20:11 ` walt
2008-01-27 8:56 ` Robert Millan
2008-01-29 5:30 ` jakllsch
2008-01-29 13:47 ` Robert Millan
2008-01-30 0:37 ` jakllsch
2008-01-30 8:56 ` Marco Gerards
2008-01-30 13:23 ` Robert Millan
2008-01-30 13:51 ` walt
2008-01-30 14:00 ` Robert Millan
2008-01-30 16:38 ` walt
2008-01-30 18:40 ` Robert Millan
2008-01-30 19:06 ` walt
2008-01-30 19:14 ` Robert Millan [this message]
2008-01-30 21:55 ` jakllsch
2008-01-31 11:03 ` Robert Millan
2008-02-01 21:11 ` walt
2008-02-01 21:38 ` Robert Millan
2008-02-04 15:32 ` Marco Gerards
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=20080130191450.GA1393@thorin \
--to=rmh@aybabtu.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.