Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#45 JS_RemoveObjectRoot’ was not declared in this scope JS_RemoveObjectRoot(cx, &root);

Unstable (example)
open
nobody
None
5
2015-02-06
2014-06-20
Barry
No

Similar to https://sourceforge.net/p/mediatomb/patches/31/ I am getting this error with the last release of Mediatomb when adding js support. This has worked previously without error on ubuntu 12.04 but I'm now on 14.04 but I'm not sure why this error would appear now since the mediatomb files haven't changed in years.
I am reviewing all the pre-reqs in case I missed something and i'll post the dpkg-buildpackage out as well if needed.
Thanks

../src/scripting/import_script.cc: In constructor ‘ImportScript::ImportScript(zmm::Ref<Runtime>)’:
../src/scripting/import_script.cc:57:56: error: ‘JS_AddNamedObjectRoot’ was not declared in this scope
JS_AddNamedObjectRoot(cx, &root, "ImportScript");
^
../src/scripting/import_script.cc: In destructor ‘virtual ImportScript::~ImportScript()’:
../src/scripting/import_script.cc:120:38: error: ‘JS_RemoveObjectRoot’ was not declared in this scope
JS_RemoveObjectRoot(cx, &root);
^
make[3]: [libmediatomb_a-import_script.o] Error 1
make[3]: Leaving directory /mediatomb/mediatomb-0.12.1/build' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory/mediatomb/mediatomb-0.12.1'
make[1]:
[all] Error 2
make[1]: Leaving directory `/mediatomb/mediatomb-0.12.1'
dh_auto_build: make -j1 returned exit code 2
make: *** [binary] Error 2
dpkg-buildpackage: error: debian/rules binary gave error exit status 2

Discussion

  • Barry
    Barry
    2014-07-24

    Anything I can do to move this along ?