Re: [gentoo-user] Cannot merge mozilla or mozilla-firefox

2005-09-25 Thread Walter Dnes
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 RRRGGGHHH N

  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



Re: [gentoo-user] Cannot merge mozilla or mozilla-firefox

2005-09-25 Thread Nagatoro

Walter Dnes wrote:

On Sat, Sep 24, 2005 at 12:26:20PM -0400, fire-eyes wrote

ACCEPT_KEYWORDS=x86 ~x86 RRRGGGHHH N

  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


Sure? I just installed a ~x86 chroot. And emerge --info shows x86 _and_ 
~x86 (only ~x86 in make.conf).



--
Naga
--
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Cannot merge mozilla or mozilla-firefox

2005-09-25 Thread fire-eyes
Zac Medico wrote:

 Your build logs show that in both cases you got segmentation faults when 
 running perl.  I suggest that you roll back to the last working version of 
 perl that you had.
 
 Zac

Well, it was the same version of perl actually, however I have remerged
it and still run into the problems. I have run perl-cleaner as well,
though of course that didn't have to do anything.

Thanks for your reply and input, it is appreciated :)
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Cannot merge mozilla or mozilla-firefox

2005-09-25 Thread Walter Dnes
On Sun, Sep 25, 2005 at 03:04:48AM -0400, Walter Dnes wrote

  A mistake has been pointed out to me in my previous reply.  Apparently
setting accept ~X86 will also accept X86.  I still believe that
accepting all of ~X86 is a bad idea.  It's the equivalant of Debian
unstable.  If you want/need a couple of packages that are masked out
~X86, then /etc/portage/package.unmask is the way to go.

-- 
Walter Dnes [EMAIL PROTECTED]
My musings on technology and security at http://tech_sec.blog.ca
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Cannot merge mozilla or mozilla-firefox

2005-09-25 Thread Walter Dnes
On Sun, Sep 25, 2005 at 06:09:15PM +0200, Nagatoro wrote

 Sure? I just installed a ~x86 chroot. And emerge --info shows x86 _and_ 
 ~x86 (only ~x86 in make.conf).

  I can make mistakes, and this looks like one.  My corrected
interpretation is that accepting *ALL* ~X86 is a problem.  If someone
needs a couple of ~X86 packages, package.unmask is the way to go.

-- 
Walter Dnes [EMAIL PROTECTED]
My musings on technology and security at http://tech_sec.blog.ca
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Cannot merge mozilla or mozilla-firefox

2005-09-25 Thread Rumen Yotov
On Sun, 25 Sep 2005 12:48:29 -0400
fire-eyes [EMAIL PROTECTED] wrote:

 Zac Medico wrote:
 
  Your build logs show that in both cases you got segmentation faults
  when running perl.  I suggest that you roll back to the last
  working version of perl that you had.
  
  Zac
 
 Well, it was the same version of perl actually, however I have
 remerged it and still run into the problems. I have run perl-cleaner
 as well, though of course that didn't have to do anything.
 
 Thanks for your reply and input, it is appreciated :)
Hi,
Check if your perl is compiled with ithreads USE-flag.
I have it ON with no problems but there's an warning in it's
description (if enabled).
HTH.Rumen


pgpqS7VzK4gcw.pgp
Description: PGP signature


Re: [gentoo-user] Cannot merge mozilla or mozilla-firefox

2005-09-25 Thread Nagatoro

Walter Dnes wrote:

  I can make mistakes, and this looks like one.  My corrected
interpretation is that accepting *ALL* ~X86 is a problem.


Not a problem per say, but it will make you use packages that are 
flagged for ebuild testing (the package *should* be stable but the 
ebuild might not be). Hence you might run into some nasty bugs but they 
should be quite unfrequent.



 If someone
needs a couple of ~X86 packages, package.unmask is the way to go.



Or rather package.keywords. package.unmask is for using packages that 
are masked in package.mask.


--
Naga
--
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Cannot merge mozilla or mozilla-firefox

2005-09-25 Thread fire-eyes
Rumen Yotov wrote:

 Hi,
 Check if your perl is compiled with ithreads USE-flag.
 I have it ON with no problems but there's an warning in it's
 description (if enabled).
 HTH.Rumen

You're right, it is on. Which is interesting, because I had problems in
the past with that, and I thought I had disabled it.

I'll take ithreads off, remerge perl and try again.

Thanks!
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Cannot merge mozilla or mozilla-firefox

2005-09-25 Thread fire-eyes
fire-eyes wrote:
 Rumen Yotov wrote:
 
 
Hi,
Check if your perl is compiled with ithreads USE-flag.
I have it ON with no problems but there's an warning in it's
description (if enabled).
HTH.Rumen
 
 
 You're right, it is on. Which is interesting, because I had problems in
 the past with that, and I thought I had disabled it.
 
 I'll take ithreads off, remerge perl and try again.
 
 Thanks!


For everyones info, libperl also looks at the ithreads USE flag. I'm
remerging libperl then perl without this USE flag (it had them both).
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Cannot merge mozilla or mozilla-firefox

2005-09-25 Thread Zac Medico
fire-eyes wrote:
 I then took off nptlonly, did an
 emerge -e world, and here I am left with tons of problems.

Note that it is not necessary to remerge anything other than glibc when the 
nptlonly flag is flipped because the nptl threading library is supposed to be 
compatible with linuxthreads.

Zac
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Cannot merge mozilla or mozilla-firefox

2005-09-25 Thread Graham Murray
Zac Medico [EMAIL PROTECTED] writes:

 Note that it is not necessary to remerge anything other than glibc
 when the nptlonly flag is flipped because the nptl threading library
 is supposed to be compatible with linuxthreads.

While in the main that is true, nptl is not completely compatible (eg
signal handling) with the old Linuxthreads. glibc is not the only
ebuild to USE the nptl flag, so maybe these ebuilds might need to be
re-emerged as well.
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Cannot merge mozilla or mozilla-firefox

2005-09-25 Thread Zac Medico
Graham Murray wrote:
 Zac Medico [EMAIL PROTECTED] writes:
 
 
Note that it is not necessary to remerge anything other than glibc
when the nptlonly flag is flipped because the nptl threading library
is supposed to be compatible with linuxthreads.
 
 
 While in the main that is true, nptl is not completely compatible (eg
 signal handling) with the old Linuxthreads. glibc is not the only
 ebuild to USE the nptl flag, so maybe these ebuilds might need to be
 re-emerged as well.

Actually, I meant to say when nptlonly and nptl flags are flipped together.   
 When they are flipped simultaneously, there is only one threading 
implementation installed (nptl is installed directly in /lib rather than 
/lib/tls).

As long as the packages that support the nptl USE flag were built with nptlonly 
and nptl both enabled or both disabled (together, simultaneously), they should 
not need to be rebuilt because both threading implementations should be binary 
compatible (though they behave differently).

Zac
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Cannot merge mozilla or mozilla-firefox

2005-09-24 Thread Zac Medico
fire-eyes wrote:
 
 p.s. - ntplonly USE flag is bad news, stay away from it.
 

Why blame random things when you have no clue what the actual problem is?  I 
for one have used nptlonly for a while with no problems.

Your build logs show that in both cases you got segmentation faults when 
running perl.  I suggest that you roll back to the last working version of perl 
that you had.

Zac
-- 
gentoo-user@gentoo.org mailing list