Your message dated Sun, 10 Jul 2016 16:23:36 +0200
with message-id <[email protected]>
and subject line closing bugs reported against ancient iceweasel versions
has caused the Debian Bug report #574833,
regarding libmozjs.so: missing symbols js_[AXY]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
574833: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574833
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libmozjs2d
Version: 1.9.1.8-5
Severity: important
I tried building gxine against libmozjs-dev 1.9.2-0preview1. It FTBFS at link
time, as follows:
script_engine.o: In function `JS_ISSPACE':
/usr/include/mozjs/jsstr.h:741: undefined reference to `js_X'
/usr/include/mozjs/jsstr.h:741: undefined reference to `js_Y'
/usr/include/mozjs/jsstr.h:741: undefined reference to `js_A'
Building against 1.9.1.8-5 works fine (which is why this bug is not of an RC
severity).
However, use of JS_CCODE, JS_ISSPACE and a few other macros will trigger this
failure in both versions since js_A, js_X and js_Y are declared as extern in
<mozjs/jsstr.h> but are not exported by the library.
--
| Darren Salt | linux at youmustbejoking | nr. Ashington, | Doon
| using Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | Army
| + It's 1984.
A hammer sometimes misses its mark - a bouquet never.
--- End Message ---
--- Begin Message ---
This bug has been reported against an ancient version of
iceweasel, that was last released with Debian 6.0 (squeeze). But
even squeeze-lts has now reached end-of-life and is no longer supported.
The bug is assumed to be fixed (or no longer relevant) in newer
firefox/firefox-esr releases and therefore I'm closing this report now.
If the problem is still reproducible in the currently supported
versions, feel free to provide more information, reopen
and reassign this bug report.
Andreas
--- End Message ---