[Bug 286906] Re: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.)
We added a mozjs source in natty which provides libmozjs185-1.0. ** Package changed: xulrunner-1.9.2 (Ubuntu) = mozjs (Ubuntu) ** Changed in: mozjs (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/286906 Title: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 286906] Re: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.)
Excerpts from Micah Gersten's message of Sun May 22 16:52:47 UTC 2011: We added a mozjs source in natty which provides libmozjs185-1.0. *WOOT!* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/286906 Title: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906]
(In reply to comment #18) * Remove the Firefox configure flag --enable-shared-js Why would we do this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/286906 Title: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906]
I think a fundamental thing here is that there's a large world between: [API changes all the time] -- ... -- [ stable API/ABI ] In particular, in the middle area, there are small things that the SpiderMonkey consuming community would greatly benefit from that don't restrict SpiderMonkey really. See https://bugzilla.mozilla.org/show_bug.cgi?id=618381 for an example. Another one is build support code for an independent-of-firefox SpiderMonkey release could be upstream, and it could have an independent version. So, let me lay out some tasks: * Land some version of 618318 so that embedders can adapt more easily when API changes * Move xulrunner/installer/mozilla-js.pc.in into js/src/ * Add a version to the libmozjs.so * Remove the Firefox configure flag --enable-shared-js * Add a make dist target that generates spidermonkey-X.tar.gz to js/src/Makefile.in -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/286906 Title: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906]
(In reply to comment #19) (In reply to comment #18) * Remove the Firefox configure flag --enable-shared-js Why would we do this? Because it conceptually conflicts with a separate spidermonkey, assuming we keep the same .so and .pc names. And if you were just interested in consuming spidermonkey, why wouldn't you use /usr/lib/libmozjs.so.42 instead of being coupled to Firefox's /usr/lib/xulrunner-1.9.x/libmozjs.so? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/286906 Title: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906]
(In reply to comment #18) * Add a make dist target that generates spidermonkey-X.tar.gz to js/src/Makefile.in AFAIK, there is no make dist target to generate source tarballs for other products. And there used to be spidermonkey releases, though it's been a while: ftp://ftp.mozilla.org/pub/mozilla.org/js/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/286906 Title: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906]
(In reply to comment #20) Because it conceptually conflicts with a separate spidermonkey, assuming we keep the same .so and .pc names. And if you were just interested in consuming spidermonkey, why wouldn't you use /usr/lib/libmozjs.so.42 instead of being coupled to Firefox's /usr/lib/xulrunner-1.9.x/libmozjs.so? Nothing prevents you to build spidermonkey from firefox and ship it in /usr/lib. That's what we do in Debian, and it has worked for a quite long time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/286906 Title: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906]
(In reply to comment #21) Nothing prevents you to build spidermonkey from firefox and ship it in /usr/lib. That's what we do in Debian, and it has worked for a quite long time. Sure, though clearly separate tarballs are better. The larger question is what you do about the mozilla-js.pc file; in this case then, xulrunner-dev wouldn't be providing it, right? Or do you have separate .pc files? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/286906 Title: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906]
(In reply to comment #20) Because it conceptually conflicts with a separate spidermonkey, assuming we keep the same .so and .pc names. And if you were just interested in consuming spidermonkey, why wouldn't you use /usr/lib/libmozjs.so.42 instead of being coupled to Firefox's /usr/lib/xulrunner-1.9.x/libmozjs.so? Note that conceptually, you'd want a --with-system-js, but I'm already not convinced bug 618318 will actually work out, so I'm doubtful about having an up-to-date configure test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/286906 Title: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906]
(In reply to comment #23) Sure, though clearly separate tarballs are better. The larger question is what you do about the mozilla-js.pc file; in this case then, xulrunner-dev wouldn't be providing it, right? Or do you have separate .pc files? $ apt-file show libmozjs-dev | grep pkgconfig libmozjs-dev: /usr/lib/pkgconfig/mozilla-js.pc $ apt-file show xulrunner-dev | grep pkgconfig xulrunner-dev: /usr/lib/pkgconfig/libxul-embedding-unstable.pc xulrunner-dev: /usr/lib/pkgconfig/libxul-embedding.pc xulrunner-dev: /usr/lib/pkgconfig/libxul-unstable.pc xulrunner-dev: /usr/lib/pkgconfig/libxul.pc xulrunner-dev: /usr/lib/pkgconfig/mozilla-gtkmozembed-embedding.pc xulrunner-dev: /usr/lib/pkgconfig/mozilla-gtkmozembed.pc xulrunner-dev: /usr/lib/pkgconfig/mozilla-plugin.pc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/286906 Title: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906]
(In reply to comment #23) (In reply to comment #21) Nothing prevents you to build spidermonkey from firefox and ship it in /usr/lib. That's what we do in Debian, and it has worked for a quite long time. Sure, though clearly separate tarballs are better. They also complicate things. See the latest security release (3.5.16/3.6.13), for instance: spidermonkey adds new symbols that xpconnect (in firefox) uses. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/286906 Title: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906]
(In reply to comment #25) $ apt-file show libmozjs-dev | grep pkgconfig libmozjs-dev: /usr/lib/pkgconfig/mozilla-js.pc Ok. Does your libxul.so (xulrunner package) depend on libmozjs.so (libmozjs package), or are they on potentially separate schedules? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/286906 Title: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906]
(In reply to comment #27) Ok. Does your libxul.so (xulrunner package) depend on libmozjs.so (libmozjs package), or are they on potentially separate schedules? Package: xulrunner-1.9.2 Depends: (...) libmozjs3d (= 1.9.2.13-1) (...) (I even force a strict dependency, version wise, though not strictly necessary) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/286906 Title: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906]
(In reply to comment #28) Package: xulrunner-1.9.2 Depends: (...) libmozjs3d (= 1.9.2.13-1) (...) (I even force a strict dependency, version wise, though not strictly necessary) (Both packages come from the same source (iceweasel) package) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/286906 Title: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906]
Bug 618318 is a little bit of a different bug. It doesn't make us 'grow up and become a ral library', but it goes about halfway there in a way which is useful for quite a number of users. Specifically, it: - packages spidermonkey separately to FF and xulrunner. - adds a major version number to the .so file, which is updated on API (and ABI as much as we can) changes - allows mozilla to keep making incompatible changes, with a new .so number - allows distributions to backport changes if they wish (in which case they would update the minor version number). - only adds a tiny burden to mozilla (remember to increase the number of API changes, and aspirationally ABI changes). It doesn't do everything distros would like (too high a burden on us), but it makes the world nicer for users. I propose we WONTFIX this bug, and move our attention to bug 618318. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/286906 Title: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906]
Wrong bug#? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/286906 Title: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906]
(In reply to comment #31) Wrong bug#? My bad, bug 618381. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/286906 Title: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] Re: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.)
** Bug watch added: Mozilla Bugzilla #618381 https://bugzilla.mozilla.org/show_bug.cgi?id=618381 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/286906 Title: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] Re: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.)
What is it about Debian's strategy that is 'right'? Are they simply packing up successive versions under different package names that can be installed in parallel, and killing off versions as soon as practical? What in the world do they do for maintenance? Cherry-picking patches from modern SpiderMonkey and adapting them to the sources from even a year ago would be heroic. -- provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) https://bugs.launchpad.net/bugs/286906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] Re: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.)
** Changed in: xulrunner Importance: Unknown = Medium -- provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) https://bugs.launchpad.net/bugs/286906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] Re: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.)
Hi, this bug is also affecting freewrl (see url at bottom) I am about to package it for debian but can't be run on lucid (unless i use a rpath workaround) ... Please build upgraded version of libmozjs-dev , if possible. For info : apt-cache rdepends libmozjs-dev libmozjs-dev Reverse Depends: xulrunner-1.9.1 libxul-dev libsablot0-dev xulrunner-1.9.1 -- http://rzr.online.fr/q/vrml -- provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) https://bugs.launchpad.net/bugs/286906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] Re: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.)
Moving to xulrunner-1.9.2 since 1.9.1 is no longer in the devel release. ** Package changed: xulrunner-1.9.1 (Ubuntu) = xulrunner-1.9.2 (Ubuntu) -- provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) https://bugs.launchpad.net/bugs/286906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] Re: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.)
This prevents people from building gxine, or at least makes it unnecessarily hard. libmozjs0d is old and should long since have been replaced with libmozjs2d (and the corresponding libmozjs-dev), built from xulrunner 1.9.*. Debian has this right… -- provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) https://bugs.launchpad.net/bugs/286906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] Re: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.)
Bug #418762 was marked as a duplicate of this bug. What can be done to remove the X11 requirements of xulrunner-1.9, particularly in regard to CouchDB's dependency? CouchDB is desirable on server installations (such as systems running chef-server, which uses CouchDB as a storage engine), and X11 is not desirable on servers. Can a xulrunner-nox packcage be created that only includes enough of xulrunner to get the spidermonkey requirement for CouchDB? -- provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) https://bugs.launchpad.net/bugs/286906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] Re: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.)
Hi, judging from the upstream bug looks like it is not going to happen, would it be possible to ship libmozjs plus the soname like e.g. what is being done in debian? (libmozjs2d for xulrunner 1.9.1) thanks -- provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) https://bugs.launchpad.net/bugs/286906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] Re: provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.)
Moving to xulrunner-1.9.1 We now have an upstream request for this. ** Summary changed: - Unable to use libmozjs.so in an application, because of library path problem. + provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) ** Bug watch added: Mozilla Bugzilla #506890 https://bugzilla.mozilla.org/show_bug.cgi?id=506890 ** Also affects: xulrunner via https://bugzilla.mozilla.org/show_bug.cgi?id=506890 Importance: Unknown Status: Unknown ** Package changed: xulrunner-1.9 (Ubuntu) = xulrunner-1.9.1 (Ubuntu) ** Changed in: xulrunner-1.9.1 (Ubuntu) Importance: Undecided = Wishlist ** Changed in: xulrunner-1.9.1 (Ubuntu) Status: Confirmed = Triaged -- provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.) https://bugs.launchpad.net/bugs/286906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] Re: Unable to use libmozjs.so in an application, because of library path problem.
Same problem here when linking a haskell program that uses gtk2hs and gtkmozembed. -- Unable to use libmozjs.so in an application, because of library path problem. https://bugs.launchpad.net/bugs/286906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] Re: Unable to use libmozjs.so in an application, because of library path problem.
Found a workaround in https://bugs.launchpad.net/ubuntu/+source/chmsee/+bug/204487. -- Unable to use libmozjs.so in an application, because of library path problem. https://bugs.launchpad.net/bugs/286906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] Re: Unable to use libmozjs.so in an application, because of library path problem.
upstream vuze beta suffers same problem -- Unable to use libmozjs.so in an application, because of library path problem. https://bugs.launchpad.net/bugs/286906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] Re: Unable to use libmozjs.so in an application, because of library path problem.
I work on the ELinks Web browser (http://elinks.cz). ELinks has (presently very minimal) support for ECMAScript via SpiderMonkey, so this issue affects ELinks as well. Until recently, I had been building ELinks with libmozjs1d and libmozjs- dev. However, xulrunner-1.9.1, on which firefox-3.5 depends, conflicts with libmozjs-dev. In order to be able to update to the latest release of Firefox, I have changed ELinks to be compatible with the new interfaces in the new xulrunner, and I have manually added some symlinks (/usr/lib/libmozjs.so - xulrunner-1.9.1.1/libmozjs.so and /usr/include/mozjs - xulrunner-1.9.1.1/unstable). ELinks's ECMAScript support is optional, and Ubuntu's ELinks package does not enable it, although Debian's does, and my own build does, so this issue with ELinks does not necessarily cause another bug in Ubuntu, but it is inconvenient for me and anybody else who wants to enable ECMAScript in ELinks on Ubuntu. Please let me know how the ELinks project should proceed to maintain compability with Ubuntu. Many thanks! -- Unable to use libmozjs.so in an application, because of library path problem. https://bugs.launchpad.net/bugs/286906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] Re: Unable to use libmozjs.so in an application, because of library path problem.
FWIW, removing libmozjs-dev and installing xulrunner-1.9-dev in karmic allowed me to build gnome-shell. -- Unable to use libmozjs.so in an application, because of library path problem. https://bugs.launchpad.net/bugs/286906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] Re: Unable to use libmozjs.so in an application, because of library path problem.
This currently breaks gnome-shell as well, because gjs uses spidermonkey. bgo bug is http://bugzilla.gnome.org/show_bug.cgi?id=573413. (I was going to link that to this bug, but the Also affects project link only talks about *upstream* bugs, and this is downstream.) -- Unable to use libmozjs.so in an application, because of library path problem. https://bugs.launchpad.net/bugs/286906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] [NEW] Unable to use libmozjs.so in an application, because of library path problem.
Public bug reported:
Binary package hint: xulrunner-1.9
source package: xulrunner-1.9
version: 1.9.0.1
ubuntu 8.04 and 8.10
I'm working on a project which depends on xulrunner and spidermonkey
(libmozjs). I use ubuntu 8.04 and xulrunner 1.9 as my development
environment. The problem is, libmozjs.so is in
/usr/lib/xulrunner-1.9.0.x/ subdir, the application can't find it if
rpath is not used. But if rpath is used, it'll be bound to a specific
version of xulrunner, which is not what we want. And there is no way to
get the correct library path of libmozjs.so by pkg-config --libs
mozilla-js.pc, which returns /usr/lib/xulrunner-devel-1.9.0.x/lib as the
library path, which is only available in xulrunner-1.9-dev package.
The content of mozilla-js.pc provided by xulrunner-1.9-dev package:
8
prefix=/usr
sdkdir=/usr/lib/xulrunner-devel-1.9.0.1
includedir=/usr/include/xulrunner-1.9.0.1
Name: JavaScript
Description: The Mozilla JavaScript Library
Version: 1.9.0.1
Requires: nspr = 3.12.0
Libs: -L${sdkdir}/lib -lmozjs
Cflags: -I${includedir}/stable -DXP_UNIX -DJS_THREADSAFE
8
You can see that there is no libdir definition in this file, and the -L
parameter points to /usr/lib/xulrunner-devel-1.9.0.1/lib, which is only
available when xulrunner-1.9-dev is installed.
Below is mozilla-js.pc from openSUSE 11:
8
prefix=/usr
sdkdir=/usr/lib64/xulrunner-devel-1.9.0.3
libdir=/usr/lib64/xulrunner-1.9
includedir=/usr/include/xulrunner-1.9.0.3
Name: JavaScript
Description: The Mozilla JavaScript Library
Version: 1.9.0.3
Requires: nspr = 4.7.1
Libs: -L${sdkdir}/lib -lmozjs
Cflags: -I${includedir}/unstable -DXP_UNIX -DJS_THREADSAFE
8
You can see that libdir is provided in this file and /usr/lib64/xulrunner-1.9
is a symbol link to the real xulrunner path(/usr/lib64/xulrunner-1.9.0.3).
Then I can use the libdir as rpath in my application and is still ok after
upgrading xulrunner to a newer version.
Besides the libdir issue, the Cflags in ubuntu's mozilla-js.pc is
incorrect, which should be -I${includedir}/unstable instead of
-I${includedir}/stable
Both ubuntu 8.04 and 8.10 have this issue.
** Affects: xulrunner-1.9 (Ubuntu)
Importance: Undecided
Assignee: Alexander Sack (asac)
Status: New
** Changed in: xulrunner-1.9 (Ubuntu)
Assignee: (unassigned) = Alexander Sack (asac)
--
Unable to use libmozjs.so in an application, because of library path problem.
https://bugs.launchpad.net/bugs/286906
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] Re: Unable to use libmozjs.so in an application, because of library path problem.
xulrunner doesnt really ship a library in the old sense. xulrunner is more a sdk + a runner. What is your use case? How do you currently try to link against it? ** Changed in: xulrunner-1.9 (Ubuntu) Status: New = Incomplete ** Changed in: xulrunner-1.9 (Ubuntu) Assignee: Alexander Sack (asac) = (unassigned) -- Unable to use libmozjs.so in an application, because of library path problem. https://bugs.launchpad.net/bugs/286906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] Re: Unable to use libmozjs.so in an application, because of library path problem.
The project I'm working on is: http://code.google.com/p/google-gadgets-for-linux, which has two modules that relies on xulrunner: 1. A script runtime module based on SpiderMonkey library(libmozjs.so), taking charge of javascript interpretation. 2. A browser module based on Gecko(gtkmozembed) and SpiderMonkey library, taking charge of html rendering. It needs inject methods into html window and run some javascript code, so only Gecko is not enough. xulrunner is the only package which provides both Gecko and SpiderMonkey. Though Gecko can be accessed via xpcomglue, SpiderMonkey can only be used as a shared library. So in this point of view, xulrunner ships not only a sdk + runner, but also a shared library. -- Unable to use libmozjs.so in an application, because of library path problem. https://bugs.launchpad.net/bugs/286906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
