grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: building grub2 on a Mac, possible bug
Date: Fri, 28 Nov 2014 21:28:35 +0200	[thread overview]
Message-ID: <5478CCE3.2020604@gmail.com> (raw)
In-Reply-To: <20141027062419.26221a73@opensuse.site>

[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]

On 27.10.2014 05:24, Andrei Borzenkov wrote:
> В Sun, 26 Oct 2014 21:00:18 -0600
> Chris Murphy <lists@colorremedies.com> пишет:
> 
>> This is on a macbookpro9,2, running Fedora 20, and I've git cloned from git://git.savannah.gnu.org/grub.git and I'm in master branch.
>>
>> $ ./configure
>> checking build system type... x86_64-unknown-linux-gnu
>> checking host system type... x86_64-unknown-linux-gnu
>> checking target system type… x86_64-unknown-linux-gnu
>>
> 
> This is normal; I get the same on openSUSE and IIRC it had always been
> the case.
> 
>> The unknown seems suspicious. And at the end I see "GRUB2 will be compiled with following components:
>> Platform: i386-pc" which is also wrong. 
>>
> 
> Well ... short of checking for /sys/firmware/efi, how can we know we
> may need efi build?
Checking fiwmware on install is ok. But not on build. Imagine a park of
x86 machines used for building. Build result should not depend on which
firmware they're running.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

  parent reply	other threads:[~2014-11-28 20:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27  3:00 building grub2 on a Mac, possible bug Chris Murphy
2014-10-27  3:24 ` Andrei Borzenkov
2014-10-27 17:46   ` Mike Gilbert
2014-10-27 18:35     ` Chris Murphy
2014-11-28 19:28   ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2014-11-29  5:30     ` Andrei Borzenkov

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=5478CCE3.2020604@gmail.com \
    --to=phcoder@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).