From: walt <wa1ter@myrealbox.com>
To: grub-devel@gnu.org
Subject: Re: Compiling grub2 on *BSD?
Date: Wed, 30 Jan 2008 08:38:23 -0800 [thread overview]
Message-ID: <fnq94r$9fc$1@ger.gmane.org> (raw)
In-Reply-To: <20080130140017.GA16576@thorin>
Robert Millan wrote:
>>> Ok, so we need __enable_execute_stack then, I guess. I find it strange that
>>> some parts of libgcc can not be used in freestanding code. Does this happen
>>> with the unpatched version of GCC too?
>>>
>>> Maybe we'll have add some dummy symbols to make it happy....
> What happens if you define the missing symbols somewhere? Any part of
> the GRUB kernel will do (e.g. kern/main.c). Just add them as empty
> functions:
>
> void
> __sysctl (void)
> {
> }
>
> void
> mprotect (void)
> {
> }
>
> and check if that works.
BTW, I just discovered that this was discussed in a thread beginning
11-30-2005 but never finished.
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, so that moddep.lst won't build.
I cheated by copying moddep.lst from my linux machine, and that allowed
the build of grub to finish, but now I get that same missing symbol when
I *run* grub. <sigh>
next prev parent reply other threads:[~2008-01-30 16:38 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 [this message]
2008-01-30 18:40 ` Robert Millan
2008-01-30 19:06 ` walt
2008-01-30 19:14 ` Robert Millan
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='fnq94r$9fc$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.