On 17/04/2008, Dennis Sacks <[EMAIL PROTECTED]> wrote:
> Matt, after I apply that patch, do I just run ./configure again or do I need
> to do something else first? I don't know how configure.ac gets used in the
> process ...
Sorry, I think you need to run the bootstrap script again ...
$ ./bootstrap -C
[...]
$ ./configure
[...]
Hopefully configure will complete correctly this time and you'll be
good to "make && make install".
Oh, just to check the obvious ;-) ... you do have the spidermonkey
development package installed right? Many Linux distributions split
packages into dev and non-dev; for example, it's called libmozjs-dev
on Ubuntu.
Hope this helps.
- Matt
> On Thu, Apr 17, 2008 at 4:53 AM, Matt Goodall <[EMAIL PROTECTED]>
> wrote:
>
>
> > On 17/04/2008, Dennis Sacks <[EMAIL PROTECTED]> wrote:
> > > ./configure outout errors with this:
> > >
> > > checking for JS_NewContext in -ljs... no
> > > checking for JS_NewContext in -lmozjs... no
> > >
> > > configure: error: Could not find the js library.
> > >
> > > Is the Mozilla SpiderMonkey library installed?
> > >
> > > I specified --with-js-lib=/usr/local/lib or without (doesn't seem to
> > matter)
> > >
> > > libjs.so is in /usr/local/lib, and /usr/local/lib is in the ld cache. I
> > > verified JS_NewContext exists as a symbol in libjs.so ...
> > >
> > > Help?!
> > >
> >
> > Try applying the attached patch to configure.ac.
> >
> > I had this problem on an Ubuntu machine. gcc doesn't seem to like
> > having non-existent directories, e.g. /opt/local, in its paths.
> >
> > Let me know if it works for you too and I'll submit a patch to the
> > issues tracker.
> >
> > - Matt
> >
>
