Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Fri, 13 Mar 2015 17:58:04 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: [GSoC] building JtR for MIC

On 2015-03-13 15:05, Lei Zhang wrote:
> Hi,
> 
> I'm kind of stuck with this autoconf problem now.
> 
> I can see macro OPENSSL_LIBS is supposed to be bound to "-lssl -lcrypto" in the following code snippet (from configure.ac):
> -----------------------------------------------------------------------------------
>    AS_IF([test "x${OPENSSL_CFLAGS}${OPENSSL_LIBS}" != "x"],
>       [AC_MSG_CHECKING([supplied paths for OpenSSL])]
>       [JTR_LIST_ADD(CFLAGS, [$OPENSSL_CFLAGS])]
>       [AC_MSG_RESULT([$OPENSSL_CFLAGS $OPENSSL_LIBS])],
>       [test "x$cross_compiling" = xno],
>       [JTR_SET_NORMAL_SSL_INCLUDES([/usr/local/ssl])]
>       [AC_CHECK_HEADER([openssl/opensslv.h],
> 	 [AC_CHECK_LIB([ssl],[SSL_library_init],
> 	    [AC_CHECK_LIB([crypto],[MD5_Update],
> 	       [AC_DEFINE(HAVE_LIBSSL,1,[Define to 1 if you have the `ssl' library (-lssl).])]
> 	       [AC_DEFINE(HAVE_LIBCRYPTO,1,[Define to 1 if you have the `crypto' library (-lcrypto).])]
> 		  [OPENSSL_LIBS="-lssl -lcrypto"],
> 	       [AC_MSG_FAILURE(JtR requires libssl/libcrypto being installed,1)])],
> 	    [AC_MSG_FAILURE(JtR requires libssl being installed,1)]
> 	 )],
> 	 [AC_MSG_FAILURE(JtR requires OpenSSL headers being installed,1)]
>       )]
>    )
> --------------------------------------------------------------------------------------
> 
> But it's strange that the binding won't happen when I configure for MIC. The configure command used is:
> $ ./configure CC=icc CFLAGS="-mmic -I$MIC/include" LDFLAGS="-mmic -L$MIC/lib" --host=mic-linux
> 
> Could anyone briefly explain to me what this code is doing? I want to figure out what's going wrong here.

There's the [test "x$cross_compiling" = xno] that will be false in your
case. For most cross-compiles, a need for supplying stuff as parameters
to ./configure is totally normal in my opinion, I wouldn't care much
about it.

Having said that, if everything is named as the autoconf system expects
things to be named, it should ideally "just work". We might miss some
pieces for this in configure.ac - very little time has been spent
testing that aspect of cross-compiles.

magnum

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ