On Sunday 20 November 2011 19:40:19 Laurent Dard wrote: > Le 20/11/2011 16:29, Serghei Amelian a écrit : > > On Sunday 20 November 2011 05:16:40 Laurent Dard wrote: > >> Le 19/11/2011 00:11, Serghei Amelian a écrit : > >>> Seems that kdm is the only kdebase application wich use > >>> libcrypt. > >> > >> Yes but I saw that kdelibs has the same problem: the crypt function > >> is not detected. > >> I fear other parts of the trinity code are affected. > > > > Where is used crypt in kdelibs? > > Nowhere, it seems, except here ;-) : > kdelibs-trinity-3.5.13/CMakeLists.txt:303:check_function_exists( crypt > HAVE_CRYPT ) kdelibs-trinity-3.5.13/config.h.cmake:75:#cmakedefine > HAVE_CRYPT 1 > > It doesn't work and seems useless: > * crypt is redefined in several files, as in: > kdelibs-trinity-3.5.13/kio/kssl/kopenssl.h:37:#define crypt > _openssl_crypt kdelibs-trinity-3.5.13/kio/kssl/kopenssl.h:50:#undef crypt > * crypt isn't invoked, as far as I can tell (encrypt or setkey) > * HAVE_CRYPT is not used either. > > Bug report: http://bugs.trinitydesktop.org/show_bug.cgi?id=654 In this case, the crypt check should be removed for kdelibs. -- Serghei