Do like me, install Virtualbox with archi686 or x86_64 (against your local install) and build in both. On Fri, Mar 20, 2009 at 2:34 PM, Abhishek Dasgupta wrote:

2009/3/20 Timm Preetz :

...

So now I have the 32bit build on my building machine, and can easily access that from my normal pc.

I there a way to upload that very 32bit build to community?

Or do I have to install "communitypkg" also on that remote machine?

I've a 32 bit chroot on my 64 bit Core 2 Duo which I use to build packages. There I manually edit ~/.tupkg and change the port; chroot and do communitypkg.

Changing the port in ~/.tupkg and issuing CARCH=i686 linux32 communitypkg should do the job, but I'm not sure.

-- Abhishek

-- Kessia Pinheiro Computer Science Student - Brazil, UFBa Linux System Administrator Arch Linux Trusted User Linux User #389695 http://even.archlinux-br.org --- X Fórum Internacional Software Livre - fisl10 24 a 27 de junho de 2009 PUCRS - Porto Alegre - Brasil

On Sun, Mar 22, 2009 at 6:17 AM, Timm Preetz wrote:

On Fri, 2009-03-20 at 14:36 -0300, Kessia 'even' Pinheiro wrote:

...

Do like me, install Virtualbox with archi686 or x86_64 (against your local install) and build in both.

Sadly no Virtualbox for me as 64bit host yet (would work, but requires some work to be done).

Also having using a spare computers save me some of my precious 2 GB RAM (which is not that much actually). I don't think it could handle another GNOME instance running inside Virtualbox.

But would you need gnome, if this is just for building packages?