Hi, I finally got the newest SDK installed, but the build stops with:
'Error while building/deploying project harbour-kitchentimer (kit:
SailfishOS-3.1.0.12-armv7hl (in Sailfish OS Build Engine))
When executing step "Start Build Engine"'
In the console it prints:
---[snip]--------------------------------------------------------------------
MerConnection: Another instance for VM "Sailfish OS Emulator 3.1.0.12" already
exists
Unknown debugger id {b69ce3fb-2375-4f3a-8b48-8706f37a3a40} in kit
SailfishOS-3.1.0.12-i486 (in Sailfish OS Build Engine)
Unknown debugger id {8cb7bb7b-818d-4143-83bc-381d48275160} in kit
SailfishOS-3.1.0.12-armv7hl (in Sailfish OS Build Engine)
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_init
qt.network.ssl: QSslSocket: cannot resolve sk_new_null
qt.network.ssl: QSslSocket: cannot resolve sk_push
qt.network.ssl: QSslSocket: cannot resolve sk_free
qt.network.ssl: QSslSocket: cannot resolve sk_num
qt.network.ssl: QSslSocket: cannot resolve sk_pop_free
qt.network.ssl: QSslSocket: cannot resolve sk_value
qt.network.ssl: QSslSocket: cannot resolve SSL_library_init
qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings
qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index
qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method
qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
qt.network.ssl: QSslSocket: cannot resolve SSLeay
qt.network.ssl: QSslSocket: cannot resolve SSLeay_version
qt.network.ssl: QSslSocket: cannot call unresolved function SSLeay
qt.network.ssl: Incompatible version of OpenSSL
VBoxManage: error: Locking of attached media failed. A possible reason is that
one of the media is attached to a running VM
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007),
component SessionMachine, interface IMachine
MerConnection: "Failed to start virtual machine \"Sailfish OS Build Engine\""
VBoxManage: error: Locking of attached media failed. A possible reason is that
one of the media is attached to a running VM
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007),
component SessionMachine, interface IMachine
MerConnection: "Failed to start virtual machine \"Sailfish OS Build Engine\""
VBoxManage: error: Locking of attached media failed. A possible reason is that
one of the media is attached to a running VM
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007),
component SessionMachine, interface IMachine
MerConnection: "Failed to start virtual machine \"Sailfish OS Build Engine\""
---[snip]--------------------------------------------------------------------
Regarding "Another instance for VM "Sailfish OS Emulator 3.1.0.12" already
exists":
I had to install/remove several times to get it in a semi-working state. One
of those times I manually removed the ~/SailfishOS and ~/.config/SailfishOS-
SDK and ~/.config/VirtualBox directories, but apparently that wasn't enough..?
Any idea on how to get this thing movin' will be much appreciated.
--
Med venlig hilsen / Best regards
Thomas Tanghus
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
