public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Boky <verynotbad@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: Emerging package as both 64 and 32 bit
Date: Sat, 16 Dec 2006 19:24:17 +0000 (UTC)	[thread overview]
Message-ID: <loom.20061216T202110-921@post.gmane.org> (raw)
In-Reply-To: em1d86$aj2$1@sea.gmane.org

Duncan <1i5t5.duncan <at> cox.net> writes:

> 
> "Boky" <verynotbad <at> gmail.com> posted
> e8666cf90612160745k19aa5622ueb3c7e84295285bc <at> mail.gmail.com, excerpted
> below, on  Sat, 16 Dec 2006 16:45:24 +0100:
> 
> > Anyways, is it possible to emerge the same package in parallel? As
> > 32-bit and 64-bit version?
> > 
> > Something in the lines of:
> > ABI="amd64,x86" emerge libxml2
> > 
> > or:
> > emerge libxml2
> > ABI="x86" emerge
> > --some-option-to-ignore-already-installed-package-and-not-remove-it
> > libxml2
> 
> 
> For a variation on the 32-bit chroot that involves creating it, then
> using it to build your own 32-bit emul- packages that you can merge on
> your 64-bit system without screwing up its database, check here.  (This is
> NOT official Gentoo, just something a Gentoo/amd64 user put up.  I'm not
> sure if it's fully upto date, but the idea will remain the same even if
> you have to tweak the specifics a bit.)  It's worth a read, anyway, just
> to see how it can be done, whether you choose to do it yourself or not.
> 
> Unofficial (User's) Gentoo/amd64 Creating your own 32-bit emul packages
> HOWTO: http://www.andyjeffries.co.uk/32bit-ebuild-amd64.html
> 

Thank you Duncan.

This is exacly what I was looking for. I have already created a 32-bit chroot,
but wasn't very keen on the idea of issuing 10+ commands (mount -o bind...) to
start openoffice or firefox.

I was experimenting with "emerge -b" but sadly, everything gets installed into
/lib so it's not usable on the main root.

I will give the mentioned link a shoot and tell you how it goes.


Cheers,
B

-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2006-12-16 20:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-16 15:45 [gentoo-amd64] Emerging package as both 64 and 32 bit Boky Boky
2006-12-16 17:09 ` Indarios
2006-12-16 18:15 ` Mike Doty
2006-12-16 18:17 ` [gentoo-amd64] " Duncan
2006-12-16 19:24   ` Boky [this message]
2006-12-16 20:08   ` Kevin F. Quinn
2006-12-16 20:41     ` Duncan
2006-12-18  9:31       ` Neil Bothwick
2006-12-18 10:22         ` Simon Stelling
2006-12-18 10:34           ` Neil Bothwick
2006-12-18 12:39           ` Duncan
2006-12-18 14:10             ` Etaoin Shrdlu
2006-12-19 15:01               ` Duncan
2006-12-20 21:49                 ` Etaoin Shrdlu
2006-12-21  9:31                   ` Duncan
2006-12-22  7:02             ` Mike Doty
2006-12-22 14:54               ` Boyd Stephen Smith Jr.
2006-12-22 21:20                 ` Duncan
2006-12-23  3:44                   ` Boyd Stephen Smith Jr.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20061216T202110-921@post.gmane.org \
    --to=verynotbad@gmail.com \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox