From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1Xuabr-0003Ti-D6 for mharc-grub-devel@gnu.org; Sat, 29 Nov 2014 00:30:19 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49149) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xuabl-0003T9-L9 for grub-devel@gnu.org; Sat, 29 Nov 2014 00:30:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xuabh-0004sb-1t for grub-devel@gnu.org; Sat, 29 Nov 2014 00:30:13 -0500 Received: from mail-lb0-x22c.google.com ([2a00:1450:4010:c04::22c]:37333) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xuabg-0004sE-QR for grub-devel@gnu.org; Sat, 29 Nov 2014 00:30:09 -0500 Received: by mail-lb0-f172.google.com with SMTP id u10so6390218lbd.31 for ; Fri, 28 Nov 2014 21:30:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type; bh=/EwMbihXJq9WXhDS+PId2OqnRJn49yEXQbsUXGzjjgw=; b=tDSW04oPN+V27vC07OONyq4wCapknCztK5jy0vxyB2szu3QHxfqjAleptWGB2Yw2Ps XqDXMoY/ofCNrUwEq65j5YACSe11p2ozugRbZF1VoWBatgQwg8Rl/ekai0pMmdr2TJP0 z47H+Kj87mVvoMqouAbPu5Ttln3JHGjZh3ABI+wZ5jQr2NY4RJrK5ykGNMud1JwUj8/W PDTeDv+tmO1qUdRfpJ1LgFIpu+hnlbhrtw6POcwfqOoVe/Rbwq9XO8uIrTeFrDRht2QY Vsv4DfNoUUdiqtIiOgXtiF56CF8NMGiQfnn2keKiy0RUDNeWk+UdDhVVgIl39OOFFWPN sF6Q== X-Received: by 10.112.130.65 with SMTP id oc1mr47388233lbb.7.1417239007987; Fri, 28 Nov 2014 21:30:07 -0800 (PST) Received: from opensuse.site (ppp91-76-15-25.pppoe.mtu-net.ru. [91.76.15.25]) by mx.google.com with ESMTPSA id n6sm3054470laj.16.2014.11.28.21.30.06 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Nov 2014 21:30:07 -0800 (PST) Date: Sat, 29 Nov 2014 08:30:04 +0300 From: Andrei Borzenkov To: Vladimir =?UTF-8?B?J8+GLWNvZGVyL3BoY29kZXIn?= Serbinenko Subject: Re: building grub2 on a Mac, possible bug Message-ID: <20141129083004.5e7f1b6b@opensuse.site> In-Reply-To: <5478CCE3.2020604@gmail.com> References: <20141027062419.26221a73@opensuse.site> <5478CCE3.2020604@gmail.com> X-Mailer: Claws Mail 3.11.0 (GTK+ 2.24.25; x86_64-suse-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/1AEDtDBNsFCrXfJEhCBqzxk"; protocol="application/pgp-signature" X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c04::22c Cc: The development of GNU GRUB X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Nov 2014 05:30:18 -0000 --Sig_/1AEDtDBNsFCrXfJEhCBqzxk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable =D0=92 Fri, 28 Nov 2014 21:28:35 +0200 Vladimir '=CF=86-coder/phcoder' Serbinenko =D0=BF=D0=B8= =D1=88=D0=B5=D1=82: > On 27.10.2014 05:24, Andrei Borzenkov wrote: > > =D0=92 Sun, 26 Oct 2014 21:00:18 -0600 > > Chris Murphy =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > >=20 > >> This is on a macbookpro9,2, running Fedora 20, and I've git cloned fro= m 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=E2=80=A6 x86_64-unknown-linux-gnu > >> > >=20 > > This is normal; I get the same on openSUSE and IIRC it had always been > > the case. > >=20 > >> The unknown seems suspicious. And at the end I see "GRUB2 will be comp= iled with following components: > >> Platform: i386-pc" which is also wrong.=20 > >> > >=20 > > 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. >=20 >=20 Actually I think defaulting to platform on which build is running makes sense. If user needs reproducible build, user should specify platform explicitly anyway. --Sig_/1AEDtDBNsFCrXfJEhCBqzxk Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlR5WdwACgkQR6LMutpd94wKAgCgwyDfm6m3zZA71qqQZrOVsLXq sIMAoIOUMOhNsyLO2DhjXQMABRZKyZW9 =xr9X -----END PGP SIGNATURE----- --Sig_/1AEDtDBNsFCrXfJEhCBqzxk--