Tiny Core Extensions > TCE 2.x

arora

<< < (3/7) > >>

Jason W:
That's good to hear, must be something else.  I am out of town and on my laptop using a custom TC 2.8 that is not the best means of testing with.  But with the openssl update, I was paying close attention to any reported ssl errors, but all seems well. 

maro:
I had not trouble reproducing the error that yoshi314 had reported (on both TC 2.8.1 and 2.9rc5). After installing 'arora.tcz' on a "plain" TC system and attempting to display a HTTPS page:
    QSslSocket: cannot call unresolved function SSLv3_client_method
    QSslSocket: cannot call unresolved function SSL_CTX_new
    QSslSocket: cannot call unresolved function SSL_library_init
    QSslSocket: cannot call unresolved function ERR_get_error
    QSslSocket: cannot call unresolved function ERR_error_string

I had a look into the 'arora.tcz.dep' file and did not see any openssl entry there. Hence I did 'tce-load -wi openssl-0.9.8m.tcz' and re-started arora. This time HTTPS pages came up time.

So, I guess: arora.tcz.dep needs an additional entry for openssl-0.9.8m.tcz

Jason W:
Since openssl support was added to qt-4.5 recently, there were dep files that needed to reflect that new dependency as anything that now depends on qt-4.5 also depends on openssl.  They have been fixed.

yoshi314:
did that fix already go into the repositories?
i've redownloaded openssl 0.9.8m just in case and i still have this


--- Code: ---arora: symbol lookup error: /usr/local/lib/libQtWebKit.so.4: undefined symbol: _ZN10QSslSocket11supportsSslEv
--- End code ---
so what am i doing wrong here?

in case i didn't mention this already - arora starts, shows up for a fraction of second, and closes.

Jason W:
Dep files were adjusted yesterday.

Navigation

[0] Message Index

[#] Next page

[*] Previous page