From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: phcoder@gmail.com
Subject: Re: Require at least gcc 4.2
Date: Thu, 3 Sep 2009 16:21:55 +0200 [thread overview]
Message-ID: <20090903142155.GD6656@thorin> (raw)
In-Reply-To: <20090901.152301.07080588.davem@davemloft.net>
On Tue, Sep 01, 2009 at 03:23:01PM -0700, David Miller wrote:
> From: "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com>
> Date: Tue, 1 Sep 2009 16:12:20 +0200
>
> > Even if gcc<4.2 seem to work ok I think we shouldn't waste resources
> > on it and officially declare a minimal requirement ("you're free to go
> > under requirement but don't post bugreports if you do")
>
> You're making it such that I won't be able to do development on my
> main sparc development machine, which is using gcc-4.1.3
>
> In my view, this is going a bit overboard as a method to address this
> problem.
Why not just skip the check? (e.g. --disable-gcc-check)
--
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."
next prev parent reply other threads:[~2009-09-03 14:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 13:44 Require at least gcc 4.2 Vladimir 'phcoder' Serbinenko
2009-09-01 14:04 ` Bean
2009-09-01 14:12 ` Vladimir 'phcoder' Serbinenko
2009-09-01 14:19 ` Bean
2009-09-01 17:02 ` Vladimir 'phcoder' Serbinenko
2009-09-01 18:11 ` Seth Goldberg
2009-09-01 22:25 ` David Miller
2009-09-01 22:23 ` David Miller
2009-09-03 14:21 ` Robert Millan [this message]
2009-09-06 15:03 ` Neil Cafferkey
2009-09-06 15:19 ` Robert Millan
2009-09-01 16:07 ` Robert Millan
2009-09-03 14:58 ` Robert Millan
2009-09-05 21:01 ` Vladimir 'phcoder' Serbinenko
2009-09-05 21:26 ` Robert Millan
2009-09-05 22:12 ` David Miller
2009-09-06 15:05 ` Robert Millan
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=20090903142155.GD6656@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
--cc=phcoder@gmail.com \
/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.