All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GRUB2 Build on Mac OS X
Date: Thu, 08 Dec 2005 21:00:18 +0100	[thread overview]
Message-ID: <878xuvmka5.fsf@xs4all.nl> (raw)
In-Reply-To: <97E8A861-43DC-47CD-AE89-10BD586C9CFD@gmail.com> (Andrei Warkentin's message of "Thu, 8 Dec 2005 13:10:08 -0600")

Andrei Warkentin <andrey.warkentin@gmail.com> writes:

Hi Andrei,

> There is another issue with GRUB2 on OS X which I am not sure has
> been brought up yet.
> Right now, AFAIK (but I haven't tested it), GRUB2 (the part that runs
> from OpenFrimware) can be built
> with a bootstrap powerpc-elf-targetted GCC hosted on OS X. However,
> the local GRUB2 binary (one that can run
> from OS X and perform installation and some such) needs to be
> compiled with the OS X compiler. Why? OS X doesn't use ELF -
> it uses Mach-O. If you want to be able to build GRUB2 in OS X with
> purely the OS X GCC, then the build procedure must take into account
> the Mach-O
> output format. AFAIK, new OpenFirmware versions (3.x) can boot Mach-O
> binaries but I haven't had a chance to experiment with this yet.

You mean the utilities like grub-setup, grub-mkimage, grub-emu, etc?
They should be able to run on macos, right?  Of perhaps I am missing
your point.

If those utilities can be build in a better way so nothing breaks and
it will work on macos, I am quite interested in hearing how to solve
that.

Mach-O binaries for booting is a different subject.  We rely on ELF
files, grub-mkimage even creates ELF files and uses ELF load
segments.  Without it GRUB just won't work, unless grub-mkimage is
changed intensively.  So it seems easier just to use ELFs in any case.

--
Marco




  reply	other threads:[~2005-12-08 20:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08  6:10 GRUB2 Build on Mac OS X Andre Smith
2005-12-08 12:26 ` Marco Gerards
2005-12-08 16:27   ` Peter Jones
2005-12-08 18:25     ` Yoshinori K. Okuji
2005-12-08 23:40       ` Peter Jones
2005-12-10  0:18         ` Yoshinori K. Okuji
2005-12-10 14:32           ` Marco Gerards
2005-12-08 18:45     ` Marco Gerards
2005-12-08 19:10     ` Andrei Warkentin
2005-12-08 20:00       ` Marco Gerards [this message]
2005-12-08 20:10         ` Andrei Warkentin
2005-12-08 20:14           ` Marco Gerards
2005-12-08 20:51             ` Andrei Warkentin
2005-12-09 22:49     ` Hollis Blanchard
2005-12-09 23:07       ` Peter Jones
2005-12-09 23:32         ` Marco Gerards
2005-12-10  0:23           ` Yoshinori K. Okuji
2005-12-10 18:52             ` Peter Jones
2005-12-09 23:26       ` Marco Gerards
2005-12-08 15:09 ` Andrei Warkentin
  -- strict thread matches above, loose matches on Subject: below --
2005-12-08 22:01 andre-smith
2005-12-08 23:06 ` Andrei Warkentin
2005-12-09 21:34   ` Marco Gerards
2005-12-08 23:18 ` Andrei Warkentin
2005-12-09 21:40 ` 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=878xuvmka5.fsf@xs4all.nl \
    --to=mgerards@xs4all.nl \
    --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.