[Slackbuilds-users] Problem building libproxy

Didier Spaier didier.spaier at epsm.fr
Wed Jul 7 07:37:40 UTC 2010

On 07/07/2010 09:07, Robby Workman wrote:
> 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-
>> in fact jsapi.h is in /usr/include/xulrunner-
>> 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- 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-
>> - 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

Thanks Erik and Robby.

I do have seamonkey installed.

I removed xulrunner and all went fine.

So, the problem seems to come from mozilla-js.pc shipped with xulrunner indicating a wrong path in its last line:
Cflags: -I${includedir}/stable -DXP_UNIX -DJS_THREADSAFE

Or may be (some of) the files in ${includedir}/unstable should be put in ${includedir}/stable instead?

Anyhow I this seems me to be a problem with xulrunner, not with libproxy.


More information about the SlackBuilds-users mailing list