Re: Report: compil error on OSX for target=i386

[Robert Millan <rmh@aybabtu.com>]

On Thu, Sep 03, 2009 at 11:33:51PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> > It's much easier to make official GCC a build requirement.  People hacking
> > on GRUB source, or distributors (e.g. Fink) should have no problem with a
> > dependency on GCC.
> >
> It won't do a lot of difference for people really wanting to compile
> GRUB. However it makes entry barrier higher.

I can't participate in a debate about an entry barrier which hasn't been
explained.  Installing GCC is a requirement, among others (autoconf, ruby,
bison...) which are no problem at all on other platforms.

Is there any reason why having build requirements is a problem on MacOS?  If
there is, how come this is not a problem for e.g. autoconf?

Does installing GCC on MacOS require significant expertise that someone who
wants to compile GRUB from source wouldn't be able to deal with?

-- 
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."