From: Daniel Barkalow <barkalow@iabervon.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Unmasking USE flags
Date: Tue, 23 Jan 2007 19:24:57 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0701231814040.20138@iabervon.org> (raw)
In-Reply-To: <200701232316.15630.bo.andresen@zlin.dk>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 1224 bytes --]
On Tue, 23 Jan 2007, Bo Ørsted Andresen wrote:
> On Tuesday 23 January 2007 22:28, Daniel Barkalow wrote:
> > Is there some approved way to unmask a USE flag that your profile masks?
> > (Maybe only for certain packages?) I need "multilib" for
> > cross-arm-elf/newlib, and x86 profiles have it masked.
> >
> > (For that matter, arm profiles seem to also have it masked, despite at
> > least some arm devices having two ISAs)
>
> I seriously doubt it'll work but unmasking a use flag is easy..
Why wouldn't it work? I'm working around an infelicity in crossdev-enabled
packages, where the USE flag for supporting multiple ABIs for the target
is masked by the profile for the build host, which is actually totally
irrelevant to the --enable-multilib configure option to (e.g.) newlib.
Is there some way to specify a totally different profile (per ARCH) for
cross-ARCH/* packages? (Ideally, it would only be somewhat seperate, in
case the build arch needs to determine some of the stuff, while the target
arch determines most of the important stuff for this sort of package.)
In any case, /etc/portage/profile is what I needed to know, thanks.
-Daniel
*This .sig left intentionally blank*
prev parent reply other threads:[~2007-01-24 0:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 21:28 [gentoo-user] Unmasking USE flags Daniel Barkalow
2007-01-23 22:16 ` Bo Ørsted Andresen
2007-01-24 0:24 ` Daniel Barkalow [this message]
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=Pine.LNX.4.64.0701231814040.20138@iabervon.org \
--to=barkalow@iabervon.org \
--cc=gentoo-user@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