From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1GwImw-0003Ic-6w for garchives@archives.gentoo.org; Mon, 18 Dec 2006 13:44:18 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id kBIDg7ft009914; Mon, 18 Dec 2006 13:42:07 GMT Received: from um1.unlimitedmail.net (139.Red-80-26-111.staticIP.rima-tde.net [80.26.111.139]) by robin.gentoo.org (8.13.8/8.13.8) with ESMTP id kBIDg4NN006336 for ; Mon, 18 Dec 2006 13:42:05 GMT Received: from ppp.zz ([137.204.208.98]) (authenticated bits=0) by um1.unlimitedmail.net (8.13.7/8.13.4) with ESMTP id kBIDfwdK019216 for ; Mon, 18 Dec 2006 14:41:59 +0100 From: Etaoin Shrdlu To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] Re: Emerging package as both 64 and 32 bit Date: Mon, 18 Dec 2006 15:10:08 +0100 User-Agent: KMail/1.9.5 References: <45866BE0.20905@gentoo.org> In-Reply-To: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Message-Id: <200612181510.08865.shrdlu@unlimitedmail.org> X-UnlimitedMail-MailScanner-From: shrdlu@unlimitedmail.org X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id kBIDg4NN006336 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by robin.gentoo.org id kBIDg7gp009914 X-Archives-Salt: 9750b1c9-e09a-4860-85f4-c9f8a45261ee X-Archives-Hash: 0b9f4bab0e47157a45fe5552dc62ff7f On Monday 18 December 2006 13:39, Duncan wrote: > My point, however, was that since everything else I run is 64-bit, if > I didn't need the 32-bit tools to compile grub -- or if I was willing > to settle for the pre-compiled grub-static -- I could save myself a > *LOT* of extra work by simply using the no-multilib subprofile, thus > saving myself all that time compiling the 32-bit side of glibc and gcc > in particular. I believe that lilo can be built in a 64-bit only environment=20 (no-multilib).=20 I use the no-multilib subprofile, and a few days ago, I found out that=20 lilo was not masked (ie, "emerge -a lilo" did prompt me to install the=20 package), so I suppose that it should work even in my 64-bit,=20 no-multilib system. (However, I did not actually merge it, since=20 grub-static still works fine here, so I can't be 100% sure). Looking at the changelog, it seems that my suppositions are correct: 06 Jan 2006; Olivier Cr=C3=AAte lilo-22.7.ebuild: Stable on amd64 So, it's been stable for almost a year now. Of course, this is not meant to be the start of another grub vs. lilo=20 flamewar, but rather just a FYI. --=20 gentoo-amd64@gentoo.org mailing list