From: walt <wa1ter@myrealbox.com>
To: grub-devel@gnu.org
Subject: Re: Compiling grub2 on *BSD?
Date: Sat, 26 Jan 2008 12:11:48 -0800 [thread overview]
Message-ID: <1201378308.10461.10.camel@k9.localnet> (raw)
In-Reply-To: <20080126172120.GA4119@thorin>
On Sat, 2008-01-26 at 18:21 +0100, Robert Millan wrote:
> On Sat, Jan 26, 2008 at 09:08:59AM -0800, walt wrote:
> > As a test of my tolerance for frustration I'm building grub2 on FreeBSD,
> > DragonFlyBSD, NetBSD, and OpenBSD, and (naturally) each build fails in a
> > different way, but all the problems seem related to mutations of gcc.
> >
> > NetBSD:
> >
> > The problem is the -nostdlib flag when linking kernel.exec.
>
> What is the problem initially?
kernel_img-kern_device.o: In function `grub_device_iterate':
../kern/device.c:84: undefined reference to `__enable_execute_stack'
That's defined in libgcc so I add -lgcc to the link flags:
/usr/lib/libgcc.a(_enable_execute_stack.o): In function
`__enable_execute_stack':
_enable_execute_stack.c:(.text+0x40): undefined reference to `__sysctl'
_enable_execute_stack.c:(.text+0x6f): undefined reference to `mprotect'
Both of those symbols are defined in libc.a, so I included that, too.
Any ideas?
> > FreeBSD:
Bean's lnxboot.S patch fixed this. Thanks Bean!
> > DragonFlyBSD:
Correction: grub2 builds correctly right out of the box. Dunno why
I had problems the first time. Black Magic!
next prev parent reply other threads:[~2008-01-26 20:12 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 [this message]
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
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=1201378308.10461.10.camel@k9.localnet \
--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.