Hi Folks I believe we should be careful with this move. I just got involved again and got my actual development environment up and running. Trying to recompile everything lead to the following
staging/i486-pc-linux-uclibc/bin/ld checking if the linker (/data2/leaf/bering-uclibc/devel/src/leaf/bering-uclibc4/buildtool/staging/i486-pc-linux-uclibc/bin/ld) is GNU ld... yes checking for shared library run path origin... done checking for libssl... no checking for libgcrypt... no configure: error: cannot find OpenSSL or Libgcrypt, try --with-libssl-prefix=PATH or --with-libgcrypt-prefix=PATH make: *** [libssh2-1.2.7/.configure] Error 1 make: Leaving directory `/data2/leaf/bering-uclibc/devel/src/leaf/bering-uclibc4/buildtool/source/libssh2' I then checked for openssh which was there, of course out of curiosityI checked openssh.patch and found the following ssl_header_ver="0x0090705FL (OpenSSL 0.9.7e 25 Oct 2004)" This I thought was pretty old and checked for the version of openSSL we are trying to use <File openssl-0.9.8r.tar.gz> I am not sure if this mismatch has any consequences, maybe noone depends on libssh2 but this is something I would not want to live with. I don't know why we need to patch configure.ac for openssh in such a drastic way, maybe someone can tell me. It will break with every new release of the underlying ssl library. cheers Erich ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
