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: Report: compil error on OSX for target=i386
Date: Sat, 5 Sep 2009 22:31:58 +0200	[thread overview]
Message-ID: <20090905203158.GB14485@thorin> (raw)
In-Reply-To: <a5d587fb0909050617l15e987a0n2d430d0ab2394cae@mail.gmail.com>

On Sat, Sep 05, 2009 at 03:17:58PM +0200, Michal Suchanek wrote:
> 
> Still the time and space required to build GCC is much larger than
> that required for building grub. The OS X platform is somewhat exotic
> because it uses different object format and non-gnu linker so it is
> more likely there will be issues with building GCC. Since the time I
> tried GCC is no longer self-containded but relies on additional
> libraries that have to be installed separately so the user has to
> compile several interdependent packages from source which certainly
> requires more planning than just building a single package.

Is there no simple mechanism for installing software on MacOS ?  E.g. on
Debian one would just use apt-get.  I heard about the Fink project,
although I haven't used it myself.

> The question here is if grub is supposed to be compatible with GNU
> systems only

We don't have this constraint.  It's fine to support non-GNU systems.  But
as a GNU project, I think it's normal that some of our dependencies are
GNU software.

Other non-GNU systems (e.g. Solaris) don't seem to have so much trouble.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



  reply	other threads:[~2009-09-05 20:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-08 14:34 Report: compil error on OSX for target=i386 Yves Blusseau
2009-08-08 14:44 ` Bean
2009-08-08 14:47   ` Vladimir 'phcoder' Serbinenko
2009-08-08 14:53     ` Bean
2009-08-10 11:41   ` Robert Millan
2009-08-22 18:00     ` Vladimir 'phcoder' Serbinenko
2009-08-23 11:00       ` Robert Millan
2009-08-23 11:10         ` Vladimir 'phcoder' Serbinenko
2009-08-28 17:29       ` Vladimir 'phcoder' Serbinenko
2009-08-31 21:10         ` Yves Blusseau
2009-09-01 11:46           ` Robert Millan
2009-09-03 21:01             ` Yves Blusseau
2009-09-04 11:48               ` Robert Millan
2009-09-05 11:47                 ` Yves Blusseau
2009-09-05 20:26                   ` Robert Millan
2009-09-03 21:33             ` Vladimir 'phcoder' Serbinenko
2009-09-04 11:59               ` Robert Millan
2009-09-05 13:17                 ` Michal Suchanek
2009-09-05 20:31                   ` Robert Millan [this message]
2009-09-05 20:59                     ` Vladimir 'phcoder' Serbinenko
2009-09-06  4:55                     ` Yves Blusseau
2009-09-06 14:54                       ` Robert Millan
2009-09-06 16:30                         ` Yves Blusseau
2009-09-06 17:17                           ` Vladimir 'phcoder' Serbinenko
2009-09-06 17:51                             ` Yves Blusseau
2009-09-06 18:56                         ` Yves Blusseau
2009-09-06 19:07                           ` Felix Zielcke
2009-09-08 14:41                           ` Robert Millan
2009-09-08 17:38                             ` Yves Blusseau

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=20090905203158.GB14485@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.