Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 353941 - [gnome-overlay] dev-libs/gjs-0.7.10 does not configure when spidermonkey is installed
Summary: [gnome-overlay] dev-libs/gjs-0.7.10 does not configure when spidermonkey is i...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
: 359039 (view as bug list)
Depends on:
Blocks: gnome3
  Show dependency tree
Reported: 2011-02-07 09:18 UTC by Guillaume ZITTA
Modified: 2012-02-12 14:11 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Guillaume ZITTA 2011-02-07 09:18:28 UTC
configure fail if spidermonkey is installed

Reproducible: Always

Steps to Reproduce:
1. emerge -1 spidermonkey
2. emerge -1 gjs

Actual Results:  
configure fail :
checking for x86_64-pc-linux-gnu-genhtml... no
checking for genhtml... /usr/bin/genhtml
checking for js-config... /usr/bin/js-config
checking for mozilla-js >= 1.9.2 ... configure: error:  >= 1.9.2 is required

Expected Results:  
gjs is merged

I have found in that :
if js-config binary (which come from spidermonkey) is found JS_PACKAGE var is not set.
So the next check fail because JS_PACKAGE is empty

I don't need spidermonkey, then unmerged it and it works now
Comment 1 Nirbheek Chauhan (RETIRED) gentoo-dev 2011-02-20 01:34:35 UTC
The initial problem of setting js-config being autodetected is fixed by just setting JS_CONFIG="". However, while linking, ld picks up the in /usr/lib/ instead of the one in /usr/lib/xulrunner-devel-*/lib/ .

If I can't figure this out, I'll have to add a blocker for spidermonkey to the ebuild...
Comment 2 Nirbheek Chauhan (RETIRED) gentoo-dev 2011-03-17 02:42:58 UTC
This is sort of fixed now, thanks for reporting.
Comment 3 Nirbheek Chauhan (RETIRED) gentoo-dev 2011-03-19 20:12:24 UTC
*** Bug 359039 has been marked as a duplicate of this bug. ***