From: Jules Colding <colding@omesc.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2
Date: Sun, 24 Jul 2005 15:28:01 +0200 [thread overview]
Message-ID: <1122211681.8105.4.camel@omc-2.omesc.com> (raw)
In-Reply-To: <42E39586.4060805@asmallpond.org>
On Sun, 2005-07-24 at 15:20 +0200, Richard Fish wrote:
> Jules Colding wrote:
> > Hmm... Among my USE flags is "nptlonly". Might that be a problem?
> >
>
> Well, nptlonly seems to work for a lot of people, so I don't think that
> should be a problem. I've only ever heard of it affecting old
> binary-only software.
I am seeing random crashes of Evolution. The backtrace originates, as
far I know, always in libpthread, so maybe this nptlonly is a bad idea
after all?
> The only change I would be tempted to make to your USE flags would be to
> add multilib, which would give you the ability to build/run both 32 and
> 64-bit applications. I don't see how this could fix your current
> problems...but I did notice that Bob Sanders (one of the two WFM reports
> on this thread) has this in his USE flags. Of course he also doesn't
> have nptlonly, or userlocales, so who knows...
Hmm... I am seeing "(-multilib)" when doing the emerge of gcc and
binutils, so multilib is disabled by my profile and shouldn't be enabled
manually, right?
Thanks,
jules
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-24 13:36 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 11:38 [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2 Jules Colding
2005-07-23 12:36 ` Patrick Börjesson
2005-07-23 12:50 ` Holly Bostick
2005-07-23 13:14 ` Jules Colding
2005-07-23 15:51 ` Patrick Börjesson
2005-07-23 16:37 ` Richard Fish
2005-07-23 17:08 ` Patrick Börjesson
2005-07-23 18:19 ` Richard Fish
2005-07-23 23:02 ` Patrick Börjesson
2005-07-24 12:43 ` Jules Colding
2005-07-25 2:09 ` Holly Bostick
2005-07-23 18:38 ` neil
2005-07-24 17:23 ` Neil Bothwick
2005-07-23 18:46 ` Bob Sanders
2005-07-23 18:51 ` Zac Medico
2005-07-23 21:26 ` Richard Fish
2005-07-24 12:28 ` Jules Colding
2005-07-24 11:07 ` Jules Colding
2005-07-24 13:20 ` Richard Fish
2005-07-24 13:28 ` Jules Colding [this message]
2005-07-24 13:51 ` Richard Fish
2005-07-24 13:57 ` Jules Colding
2005-07-24 13:58 ` Richard Fish
2005-07-24 14:27 ` Jules Colding
2005-07-24 14:43 ` Rumen Yotov
2005-07-24 14:47 ` Jules Colding
2005-07-24 15:06 ` [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2 (AMD64 users please help) Richard Fish
2005-07-24 15:12 ` Jules Colding
2005-07-24 18:10 ` Bob Sanders
2005-07-24 18:59 ` Jules Colding
2005-07-24 19:14 ` Richard Fish
2005-07-26 1:37 ` Bob Sanders
2005-07-24 14:00 ` [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2 Zac Medico
2005-07-24 15:29 ` neil
2005-07-24 12:22 ` Jules Colding
2005-07-24 12:38 ` Jules Colding
2005-07-24 12:48 ` Richard Fish
2005-07-24 13:10 ` Jules Colding
2005-07-24 13:30 ` Richard Fish
2005-07-24 13:28 ` Rumen Yotov
2005-07-24 13:35 ` Jules Colding
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=1122211681.8105.4.camel@omc-2.omesc.com \
--to=colding@omesc.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