[nodejs] node.js not compiled with openssl crypto support?

1,353 views
Skip to first unread message

nnn

unread,
May 7, 2010, 11:47:44 AM5/7/10
to nodejs
I try to install node-v0.1.94 on Ubuntu 9.10 x86_64. also I have been
install openssl.but still catch this message. why?
(node.js not compiled with openssl crypto support)
http://gist.github.com/393619

--
You received this message because you are subscribed to the Google Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com.
To unsubscribe from this group, send email to nodejs+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.

Jérémy Lal

unread,
May 7, 2010, 11:51:22 AM5/7/10
to nod...@googlegroups.com
On 07/05/2010 17:47, nnn wrote:
> I try to install node-v0.1.94 on Ubuntu 9.10 x86_64. also I have been
> install openssl.but still catch this message. why?
> (node.js not compiled with openssl crypto support)
> http://gist.github.com/393619
>

Checking for openssl : not found
Checking for function SSL_library_init : not found
Checking for header openssl/crypto.h : not found

you're missing
libssl-dev (>= 0.9.8)

Ryan Gahl

unread,
May 7, 2010, 6:14:52 PM5/7/10
to nod...@googlegroups.com
Just as an FYI on that. I noticed the exact same issue at first... and installed libssl-dev. Even after installing it, you still get the "not found" messages during ./configure on the openssl and SSL_library_init lines, but the header crypto.h is now found, and compiling via make, and then running 'make test' will (should) result in no test failures.

nnn

unread,
May 8, 2010, 4:14:25 AM5/8/10
to nodejs
Checking for header port.h : not found
Checking for header sys/event.h : not found
Checking for function kqueue : not found
Checking for library execinfo : not found

yes, after install libssl-dev, make test has not failure. but ./
configure still show above code. does it matter?



On May 8, 6:14 am, Ryan Gahl <ryan.g...@gmail.com> wrote:
> Just as an FYI on that. I noticed the exact same issue at first... and
> installed libssl-dev. Even after installing it, you still get the "not
> found" messages during ./configure on the openssl and SSL_library_init
> lines, but the header crypto.h is now found, and compiling via make, and
> then running 'make test' will (should) result in no test failures.
>
>
>
> On Fri, May 7, 2010 at 10:51 AM, Jérémy Lal <holi...@gmail.com> wrote:
> > On 07/05/2010 17:47, nnn wrote:
> > > I try to install node-v0.1.94 on Ubuntu 9.10 x86_64. also I have been
> > > install openssl.but still catch this message. why?
> > > (node.js not compiled with openssl crypto support)
> > >http://gist.github.com/393619
>
> > Checking for openssl                     : not found
> > Checking for function SSL_library_init   : not found
> > Checking for header openssl/crypto.h     : not found
>
> > you're missing
> > libssl-dev (>= 0.9.8)
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "nodejs" group.
> > To post to this group, send email to nod...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > nodejs+un...@googlegroups.com<nodejs%2Bunsu...@googlegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/nodejs?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups "nodejs" group.
> To post to this group, send email to nod...@googlegroups.com.
> To unsubscribe from this group, send email to nodejs+un...@googlegroups.com.
> For more options, visit this group athttp://groups.google.com/group/nodejs?hl=en.

Isaac Schlueter

unread,
May 8, 2010, 4:47:37 AM5/8/10
to nod...@googlegroups.com
If you don't have openssl installed, then make test skips over the ssl tests.

It only matters if you want to do https with node. I recommend
installing openssl. Crypto is cool :)

--i

nnn

unread,
May 8, 2010, 5:43:52 AM5/8/10
to nodejs
what I mean matter is these libraries not found matter.
Checking for header port.h : not found
Checking for header sys/event.h : not found
Checking for function kqueue : not found
Checking for library execinfo : not found

mscdex

unread,
May 8, 2010, 11:30:35 AM5/8/10
to nodejs
On May 8, 5:43 am, nnn <g.zhen.n...@gmail.com> wrote:
> what I mean matter is these libraries not found matter.
> Checking for header port.h               : not found
> Checking for header sys/event.h          : not found
> Checking for function kqueue             : not found
> Checking for library execinfo            : not found
>

I wouldn't worry about those errors. Some libraries and libev backends
are not available on certain platforms. My Ubuntu machine shows the
same errors. It just means node will use one of the libev backends it
_did_ find instead.

Ryan Gahl

unread,
May 8, 2010, 3:16:56 PM5/8/10
to nod...@googlegroups.com

On Sat, May 8, 2010 at 3:47 AM, Isaac Schlueter <i...@izs.me> wrote:
If you don't have openssl installed, then make test skips over the ssl tests

That was not true in my case. All tests were attempted and the crypto based ones failed, which is what I'd expect from the test suite. I then installed libssl-dev, and as the OP pointed out ./configure still results in several "not found" errors, but now the crypto.h header was found ok, and all the tests passed after recompilation. I don't know why with both openssl and libssl-dev installed, ./configure still fails to find [openssl, kqueue, execinfo] (Ubuntu 10.04 server)... but it didn't seem to matter as far as the test suite was concerned.

Nate

unread,
Jun 23, 2010, 7:16:27 PM6/23/10
to nodejs
I too got:

Checking for openssl :not found

after installing libssl-dev. However the problem is that pkg-config
is being used to check for openssl and if pkg-config is not installed
it fails and inproperly reports as openssl not found. I discovered
this by looking at config.log:

81 ----------------------------------------
82 Checking for openssl
83 pkg-config --errors-to-stdout --print-errors --cflags --libs
openssl
84 /bin/sh: pkg-config: not found
85 not found
86
87 ----------------------------------------

after sudo apt-get install pkg-config

Checking for openssl : yes

yahtzee!!


On May 7, 3:14 pm, Ryan Gahl <ryan.g...@gmail.com> wrote:
> Just as an FYI on that. I noticed the exact same issue at first... and
> installed libssl-dev. Even after installing it, you still get the "not
> found" messages during ./configure on the openssl and SSL_library_init
> lines, but the header crypto.h is now found, and compiling via make, and
> then running 'make test' will (should) result in no test failures.
>
>
>
>
>
> On Fri, May 7, 2010 at 10:51 AM, Jérémy Lal <holi...@gmail.com> wrote:
> > On 07/05/2010 17:47, nnn wrote:
> > > I try to install node-v0.1.94 on Ubuntu 9.10 x86_64. also I have been
> > > install openssl.but still catch this message. why?
> > > (node.js not compiled with openssl crypto support)
> > >http://gist.github.com/393619
>
> > Checking for openssl                     : not found
> > Checking for function SSL_library_init   : not found
> > Checking for header openssl/crypto.h     : not found
>
> > you're missing
> > libssl-dev (>= 0.9.8)
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "nodejs" group.
> > To post to this group, send email to nod...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > nodejs+un...@googlegroups.com<nodejs%2Bunsu...@googlegroups.com>
> > .

tre

unread,
Aug 31, 2011, 12:18:04 AM8/31/11
to nod...@googlegroups.com
thanks Nate, it works :D
Reply all
Reply to author
Forward
0 new messages