From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] multilib clean up
Date: Mon, 7 Mar 2011 17:29:58 -0500 [thread overview]
Message-ID: <201103071729.59324.vapier@gentoo.org> (raw)
In-Reply-To: <4D751779.5050507@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 1253 bytes --]
On Monday, March 07, 2011 12:35:53 Thomas Sachau wrote:
> Am 07.03.2011 11:24, schrieb Mike Frysinger:
> > also, i'll be converting the glibc ebuilds do always invoke the
> > multilib_env helper functions. this will allow us to drop the
> > {C,LD}FLAGS_xxx and friends from profiles since glibc was the main
> > consumer. i imagine this inadvertently break some other packages, so
> > if people want to test this on their own systems before i make the
> > commit, that'd be cool. the plan would be for said breakage will go
> > through bugzilla to get the ebuild updated rather than reverting the
> > profile.
>
> Please leave those vars in the profile, i depend on them in
> multilib-portage to crosscompile e.g. for x86 on the amd64 profile. If you
> remove them now, they would be re-added again once multilib-portage (and
> the related EAPI) become official, so imho we can just leave them in for
> now.
these need to be centralized somehow. duplicating multilib.eclass and the
profiles indefinitely isnt going to fly.
perhaps we unify all the multilib settings into one file such as
base/make.defaults ... that would require normalizing of the ABI value across
all targets, but i dont think that's an issue.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-03-07 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 10:24 [gentoo-dev] multilib clean up Mike Frysinger
2011-03-07 17:35 ` Thomas Sachau
2011-03-07 22:29 ` Mike Frysinger [this message]
2011-03-16 20:08 ` [gentoo-dev] " Mike Frysinger
2011-03-18 19:46 ` Mike Frysinger
2011-03-18 22:08 ` Mike Frysinger
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=201103071729.59324.vapier@gentoo.org \
--to=vapier@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