Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-amd64
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-amd64@g.o
From: Simon Stelling <blubb@g.o>
Subject: Re: 64-bit or 32-bit?
Date: Wed, 29 Mar 2006 17:35:17 +0200
Bertrand Jacquin wrote:
> Yes nice. But what does it do ? It compile things ? Just tarball ?
> I searched do about it, read man, read help and I still can't find
> exactly what it do. I didn't get time to look the code

It takes a x86 stage3 (which you have to download before) and a portage 
snapshot if you want it to, does all the necessary work to properly set 
up the 32bit chroot, compiles the packages you told it to, clears up 
everything, checks links for being correct and then packs everything 
into a tarball. So you end up with a tarball that looks almost exactly 
like the ones we use for app-emulation/emul-linux-x86-*.

-- 
Kind Regards,

Simon Stelling
Gentoo/AMD64 Developer
-- 
gentoo-amd64@g.o mailing list


Replies:
Re: 64-bit or 32-bit?
-- Mike Arthur
References:
64-bit or 32-bit?
-- JimD
Re: 64-bit or 32-bit?
-- Hemmann, Volker Armin
Re: 64-bit or 32-bit?
-- Jim
Re: 64-bit or 32-bit?
-- Barry . SCHWARTZ
Re: 64-bit or 32-bit?
-- Jim
Re: 64-bit or 32-bit?
-- Barry . SCHWARTZ
Re: 64-bit or 32-bit?
-- Bertrand Jacquin
Re: 64-bit or 32-bit?
-- Barry . SCHWARTZ
Re: 64-bit or 32-bit?
-- Simon Stelling
Re: 64-bit or 32-bit?
-- Barry . SCHWARTZ
Re: 64-bit or 32-bit?
-- Bertrand Jacquin
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: 64-bit or 32-bit?
Next by thread:
Re: 64-bit or 32-bit?
Previous by date:
Re: 64-bit or 32-bit?
Next by date:
Re: 64-bit or 32-bit?


Updated Jun 17, 2009

Summary: Archive of the gentoo-amd64 mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.