Summary: | media-video/gxine-0.5.905 - ld: cannot find -ljs | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
Component: | Current packages | Assignee: | Gentoo Media-video project <media-video> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | cedric.godin, Jacob.McCandless, mozilla, ooblick, SebastianLuther |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugs.xine-project.org/show_bug.cgi?id=396 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | gxine-0.5.905-r1 ebuild and patches |
Description
Juergen Rose
2010-12-30 08:59:49 UTC
Is dev-lang/spidermonkey installed? Which version? Had the same problem with dev-lang/spidermonkey-1.9.2.13 (as said in comment 1). Masked it (so now having 1.7.0-r2) and the emerge went fine. As you can see from my first posting, spidermonkey-1.9.2.13 is installed. The links to libmozjs.so without any sign of linktime resolution errors. I'd assume the same as libjs. I just added in the -lmozjs src/Makefile. Exporting the variables, the configure still fails looking for -ljs. I guess this was overridden by other options in the build. Spidermonkey built libjs_static.a. I would test this further but the build unpacks firefox... Does the threadsafe USE option have any effect? If it IS libjs then it should BE libjs ? (for all intents and purposes, albeit it's not a shared lib...) Doesn't look like gxine problem, rather spidermonkey stopped building shared library for some reason... (In reply to comment #5) > Doesn't look like gxine problem, rather spidermonkey stopped building shared > library for some reason... > The recently added spidermonkey builds libmozjs instead of libjs. Created attachment 258661 [details, diff]
gxine-0.5.905-r1 ebuild and patches
Here is everything you need for gxine to make use of current ~arch spidermonkey
works for me. -r1 in portage. pushed upstream: https://bugs.xine-project.org/show_bug.cgi?id=396 *** Bug 360971 has been marked as a duplicate of this bug. *** |