From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Moving real multilib support into main tree portage with request for council decision
Date: Sun, 11 Oct 2009 13:15:22 -0700 [thread overview]
Message-ID: <4AD23CDA.40207@gentoo.org> (raw)
In-Reply-To: <4AD1B19A.7060003@gentoo.org>
Thomas Sachau wrote:
> Hi together,
>
> as announced in a previous mail, i created a fork of portage, which has support to create 32bit libs
> during compile phase for 64bit platforms (currently amd64 tested, ppc64 untested).
>
> In short, it does execute every src_* phase twice with keeping a workdir for every ABI and saving
> some default environment vars (like *FLAGS). Since the current ABI is the last one in this order,
> the 64bit phase will overwrite everthing from 32bit phase except those parts, which have a different
> install location, so mostly libs, which go in lib32 instead of lib64.
>
> A current ebuild and docs for using it are currently in the portage-multilib branch of the multilib
> overlay.
>
> I asked zmedico about inclusion into the main svn tree of portage, but he requested a council ok
> before he would be accepting it. So this is my request for discussion and ok (in tomorrows or the
> following meeting) from the council.
An important thing to note is that there are necessary changes to
emul-* ebuilds that are technically an EAPI change, since they won't
work with old package managers that don't have support for lib32 USE
flags.
--
Thanks,
Zac
next prev parent reply other threads:[~2009-10-11 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-11 10:21 [gentoo-dev] Moving real multilib support into main tree portage with request for council decision Thomas Sachau
2009-10-11 10:55 ` Petteri Räty
2009-10-11 20:15 ` Zac Medico [this message]
2009-10-11 20:42 ` Thomas Sachau
2009-10-11 21:05 ` Mike Frysinger
2009-10-12 18:44 ` Thomas Sachau
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=4AD23CDA.40207@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-dev@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