From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
Date: Thu, 13 Oct 2011 09:53:31 -0400 [thread overview]
Message-ID: <CA+czFiDCw23zpUb7biFcCPY=pdjCgFyiF+hLq=wzL+cMzxXFkA@mail.gmail.com> (raw)
In-Reply-To: <yu9ehyhypew.fsf@nyu.edu>
On Thu, Oct 13, 2011 at 9:47 AM, Allan Gottlieb <gottlieb@nyu.edu> wrote:
> On Thu, Oct 13 2011, Michael Mol wrote:
>
>> I've skipped most of the thread, so forgive me if this was already
>> done...try rebuilding libmozjs? Bumping its version up or down?
>
> oldlap ~ # equery b /usr/lib/libmozjs185.so
> * Searching for /usr/lib/libmozjs185.so ...
> dev-lang/spidermonkey-1.8.5 (/usr/lib/libmozjs185.so -> libmozjs185.so.1.0)
> dev-lang/spidermonkey-1.8.5 (/usr/lib/libmozjs185.so.1.0.0)
>
> [I] dev-lang/spidermonkey
> Available versions: 1.7.0 (~)1.7.0-r1 (~)1.7.0-r2 1.8.2.15 {M}(~)1.8.5 {static-libs test threadsafe unicode}
> Installed versions: 1.8.5(02:22:11 PM 10/12/2011)(-static-libs -test)
>
> So the installed version is the only one from gnome3. I tried
>
> Calculating dependencies... done!
> [ebuild UD ] dev-lang/spidermonkey-1.8.2.15 [1.8.5] USE="-threadsafe% (-static-libs%) (-test%)" 50,345 kB
>
> and received a slot conflict with dev-libs/gjs.
>
> I worry trying to downgrade may lead to a string of dependencies. I can
> try it tonight if desired.
Up to you; slot conflicts are outside my area of knowledge for Gentoo.
The dmesg error you had suggests to me that the problem may be in
libmozjs. It could also be in a badly-built data structure passed
*into* libmozjs, though, so I was looking for some differential to see
which had the problem.
--
:wq
next prev parent reply other threads:[~2011-10-13 13:57 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 22:13 [gentoo-user] can't build gnome 3.2 (3.0 was ok) Allan Gottlieb
2011-10-11 22:30 ` Canek Peláez Valdés
2011-10-11 23:42 ` David Abbott
2011-10-12 1:19 ` Allan Gottlieb
2011-10-12 1:18 ` Allan Gottlieb
2011-10-12 1:37 ` Canek Peláez Valdés
2011-10-12 14:26 ` David Abbott
2011-10-12 16:52 ` Allan Gottlieb
2011-10-12 15:31 ` Allan Gottlieb
2011-10-12 16:49 ` Canek Peláez Valdés
2011-10-12 20:58 ` Allan Gottlieb
2011-10-12 21:19 ` Canek Peláez Valdés
2011-10-12 21:53 ` Allan Gottlieb
2011-10-12 22:08 ` Canek Peláez Valdés
2011-10-12 22:16 ` Michael Schreckenbauer
2011-10-12 22:25 ` Canek Peláez Valdés
2011-10-12 22:27 ` Allan Gottlieb
2011-10-12 22:52 ` Allan Gottlieb
2011-10-13 0:04 ` Canek Peláez Valdés
2011-10-13 0:02 ` Canek Peláez Valdés
2011-10-13 1:20 ` Allan Gottlieb
2011-10-13 1:36 ` Allan Gottlieb
2011-10-13 4:10 ` Canek Peláez Valdés
2011-10-13 13:39 ` Allan Gottlieb
2011-10-13 8:58 ` Michael Schreckenbauer
2011-10-13 13:29 ` Allan Gottlieb
2011-10-13 13:36 ` Michael Mol
2011-10-13 13:47 ` Allan Gottlieb
2011-10-13 13:53 ` Michael Mol [this message]
2011-10-13 15:05 ` Michael Schreckenbauer
2011-10-14 1:03 ` Allan Gottlieb
2011-10-12 21:40 ` Michael Schreckenbauer
2011-10-12 22:02 ` Allan Gottlieb
2011-10-12 22:10 ` Michael Schreckenbauer
2011-10-12 22:46 ` Allan Gottlieb
2011-10-13 0:03 ` Canek Peláez Valdés
2011-10-13 13:34 ` Allan Gottlieb
2011-10-13 18:45 ` Canek Peláez Valdés
2011-10-14 1:20 ` Allan Gottlieb
2011-10-14 1:58 ` Canek Peláez Valdés
2011-10-14 2:44 ` Allan Gottlieb
-- strict thread matches above, loose matches on Subject: below --
2011-10-13 12:21 Denis I. Polukarov
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='CA+czFiDCw23zpUb7biFcCPY=pdjCgFyiF+hLq=wzL+cMzxXFkA@mail.gmail.com' \
--to=mikemol@gmail.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