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.54) id 1FOf3t-0002C4-Hh for garchives@archives.gentoo.org; Wed, 29 Mar 2006 18:06:30 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.6/8.13.5) with SMTP id k2THwFLk009477; Wed, 29 Mar 2006 17:58:15 GMT Received: from asmtp-out6.blueyonder.co.uk (asmtp-out6.blueyonder.co.uk [195.188.213.65]) by robin.gentoo.org (8.13.6/8.13.5) with ESMTP id k2THwE9N012978 for ; Wed, 29 Mar 2006 17:58:14 GMT Received: from [82.41.205.190] (helo=mp5.mikearthur.co.uk) by asmtp-out6.blueyonder.co.uk with esmtpa (Exim 4.52) id 1FOevt-0000Z1-WA for gentoo-amd64@lists.gentoo.org; Wed, 29 Mar 2006 18:58:14 +0100 Received: from m249 (m249 [192.168.0.100]) by mp5.mikearthur.co.uk (Postfix) with ESMTP id A95AC50C6D for ; Wed, 29 Mar 2006 19:08:48 +0100 (BST) From: Mike Arthur To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] 64-bit or 32-bit? Date: Wed, 29 Mar 2006 18:58:24 +0100 User-Agent: KMail/1.9.1 References: <20060326103301.7e4228b6@keelie.localdomain> <200603291825.49407.mike@mikearthur.co.uk> <442AC5A9.4020201@gentoo.org> In-Reply-To: <442AC5A9.4020201@gentoo.org> 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="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603291858.24449.mike@mikearthur.co.uk> X-Archives-Salt: f7e9a154-28c1-4b88-875e-c0ee37ada926 X-Archives-Hash: 1fb9debe4aa786b3ea7f103b17c0ef19 On Wednesday 29 March 2006 18:36, Simon Stelling wrote: > Mike Arthur wrote: > > If I already have a 32-bit chroot set up, how would I go about creating > > emul- or -bin packages from this chroot? > > Setting tmpdir=/path/to/your/chroot in /etc/emool/emool.conf should do > the trick. However, be careful, it'll overwrite /root/.bash_profile to > start itself inside the chroot. So if you use that chroot for other > things too, you have to back it up first (or just delete it afterwards > if it didn't exist before). Cool. What I meant though, is how I'd do that without emool, sorry! -- gentoo-amd64@gentoo.org mailing list