On Sat, Sep 24, 2005 at 12:26:20PM -0400, fire-eyes wrote
> Hello, I am hoping I can get some assistance here. These problems are
> probably specific to my system. These and many other irritants cropped
> up after I enabled nptl and nptlonly. I then took off nptlonly, did an
> emerge -e world, and here I am left with tons of problems.
nptl and nptlonly work fine on my system, including firefox.
> ACCEPT_KEYWORDS="x86 ~x86" AAAAAAAARRRRRRRGGGGGGGHHHHHHH NNNNNOOOO!!!!
ACCEPT_KEYWORDS="~x86" is OK (sort of) if you want strictly testing
and bleeding edge. Expect some breakage along the way, but it shouldn't
die on you. However, mixing X86 *AND* ~X86 in ACCEPT_KEYWORDS is a
*BAD* idea. You'll get a mish-mash of stable and unstable stuff and
guaranteed problems. If you want a stable system, you want
ACCEPT_KEYWORDS="x86". That happens to be the default on X86 systems.
I can't offer any advice other than blowing away the OS and
re-installing from scratch (you do have your data files on a separate
partition?).
Note, if you want only a handful of ~X86 packages, it can be done on
an individual basis. Leave your system as X86. For that package that
you gotta have, regardless of whether it's ready or not, enter it in
/etc/portage/package.unmask. "man portage" and look up "package.unmask"
for details.
> MAKEOPTS="-j3" Doesn't help either, but it's minor in comparison.
Unless you have a multi-CPU (or multi-core) you shouldn't exceed "-j2".
Even then, there are rare occasions when you need to drop down "-j1".
BTW, you should use...
CXXFLAGS="${CFLAGS}"
after you've set CFLAGS. This guarantees synchronization.
--
Walter Dnes <[EMAIL PROTECTED]>
My musings on technology and security at http://tech_sec.blog.ca
--
gentoo-user@gentoo.org mailing list
