All of lore.kernel.org
 help / color / mirror / Atom feed
From: jacob berkman <jacob@87k.net>
To: grub-devel@gnu.org
Cc: jacob berkman <jacob@87k.net>
Subject: [PATCH 0/3] A few small OpenBSD-ish fixes
Date: Tue, 18 May 2021 22:14:12 -0700	[thread overview]
Message-ID: <20210519051415.847-1-jacob@87k.net> (raw)

Hello,

I built GRUB on OpenBSD 6.9 over the weekend, and ran into a few
issues. The minor ones attached were easy enough to
fix. Unfortunately, once installed, it merely prints "Grub Loading"
(or something similar) and reboots. In trying to recover from this, I
wiped out the MBR and that's when I gave up and figured maybe I should
do this in a VM instead.

One other issue I ran into was that setjmp.mod would fail to build
because it didn't export any symbols. No other modules seemed to
depend on it. I just removed it from Makefile, but I'm not familiar
enough with GRUB to know whether that's a reasonable enough solution,
or if that's related to the inability to boot.

Cheers,
 // jacob

jacob berkman (3):
  Do not fail configure if Python is missing. It's only required for
    developement of GRUB.
  Fix warning about misleading indentation on OpenBSD 6.9 with -Werror
    enabled (which is the default).
  Use size_t printf format to match type

 configure.ac            | 2 +-
 grub-core/fs/zfs/zfs.c  | 4 ++--
 grub-core/lib/LzmaEnc.c | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

-- 
2.30.1 (Apple Git-130)



             reply	other threads:[~2021-05-19  5:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19  5:14 jacob berkman [this message]
2021-05-19  5:14 ` [PATCH 1/3] Do not fail configure if Python is missing. It's only required for developement of GRUB jacob berkman
2021-05-19  5:14 ` [PATCH 2/3] Fix warning about misleading indentation on OpenBSD 6.9 with -Werror enabled (which is the default) jacob berkman
2021-05-19  5:14 ` [PATCH 3/3] Use size_t printf format to match type jacob berkman
2021-05-27 14:58 ` [PATCH 0/3] A few small OpenBSD-ish fixes Daniel Kiper

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=20210519051415.847-1-jacob@87k.net \
    --to=jacob@87k.net \
    --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.