All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Compiling grub2 on *BSD?
Date: Tue, 29 Jan 2008 14:47:07 +0100	[thread overview]
Message-ID: <20080129134707.GF27435@thorin> (raw)
In-Reply-To: <20080129053051.GY1341@kirkkit.kollasch.net>

On Mon, Jan 28, 2008 at 11:30:51PM -0600, jakllsch@kollasch.net wrote:
> On Sun, Jan 27, 2008 at 09:56:50AM +0100, Robert Millan wrote:
> > On Sat, Jan 26, 2008 at 12:11:48PM -0800, walt wrote:
> > > > 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?
> > 
> > Do you see this line in ./configure ?
> > 
> >   checking whether `gcc' accepts `-fstack-protector'... yes
> 
> Yes.
> 
> Apparently -fno-stack-protector doesn't actually work the way
> I/we would expect.
> 
> But, I'm surprised that this doesn't affect the building
> of NetBSD's own 'stand' code.

Maybe we need another flag?  Could you check the link command in NetBSD's
kernel ?

-- 
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 /.)



  reply	other threads:[~2008-01-29 13:48 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 [this message]
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=20080129134707.GF27435@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.