From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH 2/2] RFT: Remove ABS macro from boot/i386/pc/boot.S
Date: Sat, 18 Jul 2009 21:16:22 +0200 [thread overview]
Message-ID: <20090718191622.GL8867@thorin> (raw)
In-Reply-To: <d7ead6de0907181134y7f5041ccgcde897995afe2ab8@mail.gmail.com>
On Sat, Jul 18, 2009 at 08:34:41PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> Haiku can be compiled and can use either gcc 4.x or gcc2.95. The main
> reason for them to keep gcc 2.95 possibility is the binary
> compatibility with BeOS. As François Revol explained me on IRC C++ ABI
> changed from gcc2 to gcc3 and as BeOS and Haiku heavily rely on C++
> it's impossible to launch BeOS apps under Haiku if it was compiled
> with gcc4.
Ok, but this doesn't seem to be related to GRUB, since we don't need to
link its utils with any proprietary code. Can't they compile runtime
libraries intended for BeOS compatibility using gcc2 and use gcc4 for
GRUB (and, well, just about everything else)?
--
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-07-18 19:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 3:47 [PATCH 1/2] RFT: Eliminate Apple specific code from boot/i386/pc/boot.S Pavel Roskin
2009-07-16 3:47 ` [PATCH 2/2] RFT: Remove ABS macro " Pavel Roskin
2009-07-18 15:17 ` Vladimir 'phcoder' Serbinenko
2009-07-18 18:22 ` Robert Millan
2009-07-18 18:34 ` Vladimir 'phcoder' Serbinenko
2009-07-18 19:16 ` Robert Millan [this message]
2009-08-07 17:15 ` Vladimir 'phcoder' Serbinenko
2009-08-13 5:53 ` Pavel Roskin
2009-07-16 16:31 ` [PATCH 1/2] RFT: Eliminate Apple specific code " Vladimir 'phcoder' Serbinenko
2009-08-13 5:21 ` Pavel Roskin
2009-08-08 14:48 ` [PATCH] RFT: Rename local labels with a macro " Yves Blusseau
2009-08-08 14:55 ` Vladimir 'phcoder' Serbinenko
2009-08-08 15:47 ` Yves Blusseau
2009-08-10 11:29 ` Robert Millan
2009-08-13 6:13 ` Pavel Roskin
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=20090718191622.GL8867@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.