Yeah, I fixed this by compiling qt with node's ssl library. Of course, this will be more troublesome for people so I guess I may have to include binary libraries inside the npm package or get complaints from everyone who can't "node-gyp rebuild" it on their systems. And when I use this newly compiled qt library with node v0.6, it segfaults somewhere inside ssl, so I guess it requires separate qt libraries depending on node version.
Side question: is it possible to configure a .gyp binding file that would somehow create a linking command that looks like this? cmd_solink = $(LINK.$(TOOLSET)) -shared $(GYP_LDFLAGS) $(LDFLAGS.$(TOOLSET)) -Wl,-soname=$(@F) -o $@ -Wl,--whole-archive $(LD_INPUTS) $(LIBS) -Wl,--no-whole-archive The difference is that $(LIBS) is included in the --whole-archive section so that all the symbols in the libraries get shoved into final binary. On Tue, Jun 26, 2012 at 6:47 AM, Ben Noordhuis <i...@bnoordhuis.nl> wrote: > On Tue, Jun 26, 2012 at 5:35 AM, Dean Mao <dean...@gmail.com> wrote: > > I ran it with gdb, it looks like it crashed in SSL_library_init(). I > also > > ran ldd on node 0.6.19 and saw that libssl & crypto are shown there, yet > in > > node 0.8.0 they are not linked -- does node 0.8.0 rely on external > modules > > for ssl support? > > As Robert pointed out, we bundle openssl and link it statically into > the node binary. > > Does libqt link to openssl somehow? If yes, there's your problem - > it's linking to another version of openssl. >
