[Slackbuilds-users] Problem building libproxy

Robby Workman rworkman at slackbuilds.org
Wed Jul 7 07:07:39 UTC 2010


On Wed, 07 Jul 2010 00:32:38 +0200
Didier Spaier <didier.spaier at epsm.fr> wrote:

> Hi all,
> 
> trying to build libproxy on Slackware64-13.1 it failed because
> jsapi.h, referenced in
> libproxy-0.4.2/libproxy/modules/pacrunner_mozjs.cpp:34 was not found.
> 
> Having read the thread
> http://code.google.com/p/libproxy/issues/detail?id=18 I notice that
> though I get this: bash-4.1$ pkg-config --cflags mozilla-js -DXP_UNIX
> -DJS_THREADSAFE -I/usr/include/xulrunner-1.9.1.7/stable
> 
> in fact jsapi.h is in /usr/include/xulrunner-1.9.1.7/unstable
> 
> Thus as I edited /usr/lib64/pkgconfig/mozilla-js.pc with
> s/stable/unstable/ and then I could build successfully libproxy.
> 
> So my questions are:
> - I had installed previously xulrunner-1.9.1.7 because I needed it
> for something else. Is it a dependency of libproxy, though this be
> not indicated in the README ?
> - Is there a packaging problem with xulrunner-1.9.1.7?
> - May-be the file jsapi.h was expected from another package but which
> one? I have another one in /usr/include/seamonkey-2.0.5/js but it is
> not seen at build time.


About all I can tell you is that it builds fine on a stock system.
Probably you need seamonkey installed.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20100707/f187d1cf/attachment.asc>


More information about the SlackBuilds-users mailing list