From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: flags on a minimalist server
Date: Thu, 10 Sep 2009 14:41:39 +0000 (UTC) [thread overview]
Message-ID: <loom.20090910T163604-366@post.gmane.org> (raw)
In-Reply-To: 92ad22480909100414u53f7b5e7o3f2877a61592a6a4@mail.gmail.com
Crístian Viana <cristiandeives <at> gmail.com> writes:
> Ebuils that need xml support don't have a USE flag for it. Only those where
it's optional.
> python has optional XML support, but gentoolkit needs that feature.--
OK I got the xml flag issue resolved, but what about the "threads" flag"?
From my original post:
USE="-* -nls mmx hardened ncurses ssl crypt berkdb tcpd pam perl pcre \
python readline zlib bzip2 nptl nptlonly syslog"
so nptl and nptlonly flags are set. -* means most other flags are unset.
To rebuild python, it want the xml flag set for gentoolkit (got it).
But also it shows "-threads" flag as not set.
dev-lang/python-2.6.2-r1 USE="berkdb ncurses readline ssl
-build -doc -examples -gdbm* -ipv6* -sqlite -threads* -tk -ucs2 -wininst -xml*"
Is this a good idea or bad idea to leave the "-threads" flag unset
in rebuilding python or any other package on this mostly iptables firewall?
(even though nptl and nptlonly are set) ????
Where can I read up on the flags in some detail?
James
next prev parent reply other threads:[~2009-09-10 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 18:56 [gentoo-user] flags on a minimalist server James
2009-09-09 19:16 ` Crístian Viana
2009-09-09 20:22 ` [gentoo-user] " Nikos Chantziaras
2009-09-09 22:17 ` James
2009-09-10 19:16 ` Nikos Chantziaras
2009-09-10 11:14 ` Crístian Viana
2009-09-10 14:41 ` James [this message]
2009-09-10 17:36 ` Crístian Viana
2009-09-11 2:24 ` [gentoo-user] ReSolved: " James
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.20090910T163604-366@post.gmane.org \
--to=wireless@tampabay.rr.com \
--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