5 Jan
2017
5 Jan
'17
2:57 a.m.
This is the error I get
cd /opt/software_x64/KDE/TDE/tdebase/obj-x86_64-linux-gnu/kdesktop/lock &&
/usr/bin/g++ -DHAVE_CONFIG_H -DSMB_CTX_FLAG_USE_KERBEROS
-DSMB_CTX_FLAG_FALLBACK_AFTER_KERBEROS -g -Wall -D_FORTIFY_SOURCE=2
-fvisibility=hidden -fvisibility-inlines-hidden -DQT_NO_ASCII_CAST
-DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION
-DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -I/usr/include/tqt3
-I/usr/include/tqt -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL
-DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT
-include tqt.h
-I/opt/software_x64/KDE/TDE/tdebase/obj-x86_64-linux-gnu/kdesktop/lock
-I/opt/software_x64/KDE/TDE/tdebase/obj-x86_64-linux-gnu/kdesktop
-I/opt/software_x64/KDE/TDE/tdebase/obj-x86_64-linux-gnu
-I/opt/software_x64/KDE/TDE/tdebase/tdmlib
-I/opt/software_x64/KDE/TDE/tdebase/kcheckpass -I/opt/trinity/include
-I/usr/include/tqt3 -I/usr/include/tqt -o
CMakeFiles/kdesktop_lock.dir/lockdlg.cc.o -c
/opt/software_x64/KDE/TDE/tdebase/kdesktop/lock/lockdlg.cc
/opt/software_x64/KDE/TDE/tdebase/kdesktop/lock/lockdlg.cc: In member
function 'virtual void PasswordDlg::attemptCardLogin()':
/opt/software_x64/KDE/TDE/tdebase/kdesktop/lock/lockdlg.cc:979:7: error:
'pkcsLoginEnabled' is not a member of 'LDAPManager'
if (!LDAPManager::pkcsLoginEnabled()) {
^
kdesktop/lock/CMakeFiles/kdesktop_lock.dir/build.make:122: recipe for
target 'kdesktop/lock/CMakeFiles/kdesktop_lock.dir/lockdlg.cc.o' failed
make[3]: *** [kdesktop/lock/CMakeFiles/kdesktop_lock.dir/lockdlg.cc.o]
Error 1
make[3]: Leaving directory
'/opt/software_x64/KDE/TDE/tdebase/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:22924: recipe for target
'kdesktop/lock/CMakeFiles/kdesktop_lock.dir/all' failed
On Thu, Jan 5, 2017 at 8:55 AM, deloptes <deloptes(a)gmail.com> wrote:
Michele Calgaro wrote:
If you are building using jessie (as you
mentioned in another email) it
sounds a little strange you had to disable pkcs support. openssl in
jessie
is still at 1.0.1 (or 1.0.2 with backport)...
Just for info only.
There were also some other minor things, but I was having another goal.
Perhaps when scripts are available I will setup a build env and report on
issues with that. For the openssl you are correct. I have openssl 1.0.1t
here.
$ dpkg -l | grep openssl
ii libevent-openssl-2.0-5:amd64 2.0.21-stable-2
amd64 Asynchronous event notification library (openssl)
ii libgnutls-openssl27:amd64 3.3.8-6+deb8u3
amd64 GNU TLS library - OpenSSL wrapper
ii openssl 1.0.1t-1+deb8u5
amd64 Secure Sockets Layer toolkit - cryptographic utility
ii openssl-blacklist 0.5-3
all Blacklists for OpenSSL RSA keys and tools
ii python-openssl 0.14-1
all Python 2 wrapper around the OpenSSL library
regards
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe@
lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help@lists.
pearsoncomputing.net
Read list messages on the web archive: http://trinity-devel.
pearsoncomputing.net/
Please remember not to top-post: http://trinity.
pearsoncomputing.net/mailing_lists/#top-posting