[Bug 232402] [NEW] chmsee does not build in Hardy

Launchpad Bug Tracker 232402 at bugs.launchpad.net
Tue Jun 10 13:51:12 BST 2008


You have been subscribed to a public bug by Saïvann Carignan (saivann):

Binary package hint: chmsee

chmsee does not build in Hardy. It seems to be caused by latest
xulrunner-devel version. Bug #204487 also says that chmsee does not
start at all in Hardy because of latest libxul version.

This might be fixed in the latest 1.0.1 version.

...
/usr/lib/xulrunner-devel-1.9b5/lib/libxul.so: undefined reference to `JS_HashTableLookup'
/usr/lib/xulrunner-devel-1.9b5/lib/libxul.so: undefined reference to `JS_SetReservedSlot'
/usr/lib/xulrunner-devel-1.9b5/lib/libxul.so: undefined reference to `sqlite3_value_int'
/usr/lib/xulrunner-devel-1.9b5/lib/libxul.so: undefined reference to `JS_SetExecuteHook'
/usr/lib/xulrunner-devel-1.9b5/lib/libxul.so: undefined reference to `JS_SetOperationLimit'
/usr/lib/xulrunner-devel-1.9b5/lib/libxul.so: undefined reference to `JS_AddNamedRootRT'
/usr/lib/xulrunner-devel-1.9b5/lib/libxul.so: undefined reference to `JS_RemoveRoot'
collect2: ld returned 1 exit status
make[4]: *** [chmsee] Error 1
make[4]: Leaving directory `/tmp/buildd/chmsee-1.0.0/src'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/tmp/buildd/chmsee-1.0.0/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/buildd/chmsee-1.0.0'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/buildd/chmsee-1.0.0'
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: failure: debian/rules build gave error exit status 2
pbuilder: Failed autobuilding of package
 -> Aborting with an error
 -> unmounting dev/pts filesystem
 -> unmounting proc filesystem
 -> cleaning the build env 
    -> removing directory /var/cache/pbuilder/build//10104 and its subdirectories

** Affects: chmsee (Ubuntu)
     Importance: Medium
     Assignee: Saïvann Carignan (saivann)
         Status: In Progress

-- 
chmsee does not build in Hardy
https://bugs.edge.launchpad.net/bugs/232402
You received this bug notification because you are a member of Ubuntu Sponsors for universe, which is a direct subscriber.



More information about the Ubuntu-universe-sponsors mailing list