but without tls support node useless.
1) download opnessl sources from openssl.org
2) ./config shared
3) cd ../node-v0.6.13
4) export PYTHON=python2.4;export CC="/usr/bin/gcc4";export CXX="/usr/
bin/g++4";./configure --openssl-includes=/usr/local/ssl/include/ --
openssl-libpath=/usr/local/ssl/lib/
5) make
P.S.: if you got these errors:
../src/node_crypto.cc: In static member function ‘static void
node::crypto::Connection::SSLInfoCallback(const SSL*, int, int)’:
../src/node_crypto.cc:999: error: invalid conversion from ‘const SSL*’
to ‘SSL*’
../src/node_crypto.cc:999: error: initializing argument 1 of ‘void*
SSL_get_ex_data(SSL*, int)’
../src/node_crypto.cc:1004: error: invalid conversion from ‘const
SSL*’ to ‘SSL*’
../src/node_crypto.cc:1004: error: initializing argument 1 of ‘void*
SSL_get_ex_data(SSL*, int)’
change
line 999: Connection* c =
static_cast<Connection*>(SSL_get_app_data(ssl));
to: Connection* c =
static_cast<Connection*>(SSL_get_app_data((SSL*)ssl));
line 1004: Connection* c =
static_cast<Connection*>(SSL_get_app_data(ssl));
to: Connection* c =
static_cast<Connection*>(SSL_get_app_data((SSL*)ssl));
On Mar 21, 12:53 pm, Dmitry Bochkarev <[email protected]> wrote:
> Hello everyone. I just compile node v 0.6.13 in CentOS 4.
>
> 1) in file src/node_zlib.cc comment
> line 217 'strategy == Z_FIXED ||'
> line 341 'NODE_DEFINE_CONSTANT(target, Z_FIXED);'
> 2) export PYTHON=python2.4;export CC="/usr/bin/gcc4";export CXX="/usr/
> bin/g++4";./configure --without-snapshot --without-ssl --no-ssl2
> 3) make
>
> Hope this help.
>
> On 14 фев, 16:06, steve johnston <[email protected]> wrote:
>
>
>
>
>
>
>
> > Ben, thanks for your help. I am not going to pursue this any further.
> > Steve
>
> > On Mon, Feb 13, 2012 at 5:01 AM, Ben Noordhuis <[email protected]> wrote:
> > > On Mon, Feb 13, 2012 at 04:24, steve johnston
> > > <[email protected]> wrote:
> > > > Hello Ben, I applied the patch. It does create the 'out' dir. But that's
> > > > about it:
>
> > > >>make
> > > > tools/gyp_node -f make
> > > > output_dir: /usr/local/src/joyent-node-d4ccdea/out
>
> > > > make -C out BUILDTYPE=Release
> > > > make[1]: Entering directory `/usr/local/src/joyent-node-d4ccdea/out'
> > > > make[1]: Nothing to be done for `all'.
> > > > make[1]: Leaving directory `/usr/local/src/joyent-node-d4ccdea/out'
> > > > ln -fs out/Release/node node
>
> > > > out>ls
> > > > deps Makefile node_js2c.host.mk node.target.mk
>
> > > Okay, so gyp is producing the expected makefiles, they just don't seem
> > > to do anything.
>
> > > What does `make -v` say? You probably need at least GNU make 3.80
> > > though I personally can only vouch for 3.81 and newer.
>
> > > If your make is up to date, can you try the upgrade-gyp branch from
> > > the joyent/node repository? I didn't see any likely culprits in gyp's
> > > changelog but it's worth a shot.
>
> > > --
> > > Job Board:http://jobs.nodejs.org/
> > > Posting guidelines:
> > >https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> > > You received this message because you are subscribed to the Google
> > > Groups "nodejs" group.
> > > To post to this group, send email to [email protected]
> > > To unsubscribe from this group, send email to
> > > [email protected]
> > > For more options, visit this group at
> > >http://groups.google.com/group/nodejs?hl=en?hl=en
>
> > --
> > Thanks,
>
> > Steve
> > [email protected]
> > 206-406-8100
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
