From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH v2 5/7] m4: Fix libcrypto detection on 32-bit cross build
Date: Mon, 9 Oct 2017 17:43:23 +0200 [thread overview]
Message-ID: <20171009154322.GG25633@rei.lan> (raw)
In-Reply-To: <20171009110101.3329-6-pvorel@suse.cz>
Hi!
> diff --git a/configure.ac b/configure.ac
> index 4eb61e070..89647ba17 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -32,22 +32,23 @@ AC_PREFIX_DEFAULT(/opt/ltp)
>
> AC_CHECK_HEADERS([ \
> ifaddrs.h \
> - libaio.h \
> - mm.h \
> - pthread.h \
> - sys/xattr.h \
> keyutils.h \
> + libaio.h \
> linux/can.h \
> linux/genetlink.h \
> linux/keyctl.h \
> linux/mempolicy.h \
> linux/module.h \
> linux/netlink.h \
> + mm.h \
> + openssl/sha.h \
> + pthread.h \
> sys/acl.h \
> sys/epoll.h \
> - sys/inotify.h \
> sys/fanotify.h \
> + sys/inotify.h \
> sys/prctl.h \
> + sys/xattr.h \
> ])
Can we sort these in a separate patch please?
> # Tools knobs
> diff --git a/m4/ltp-crypto.m4 b/m4/ltp-crypto.m4
> index 3dfc51266..d066ab7e0 100644
> --- a/m4/ltp-crypto.m4
> +++ b/m4/ltp-crypto.m4
> @@ -2,8 +2,10 @@ dnl
> dnl LTP_CHECK_CRYPTO
> dnl ----------------------------
> dnl
> -AC_DEFUN([LTP_CHECK_CRYPTO],
> -[dnl
> -AC_CHECK_HEADERS(openssl/sha.h,[CRYPTO_LIBS=-lcrypto],[CRYPTO_LIBS=])
> -AC_SUBST(CRYPTO_LIBS)
> +AC_DEFUN([LTP_CHECK_CRYPTO], [
> + AC_CHECK_LIB([crypto], [SHA1_Init], [crypto_libs="-lcrypto"])
> + AC_SUBST([CRYPTO_LIBS], [$crypto_libs])
> + if test "x$have_libnuma" != "x"; then
^
Typo?
> + AC_DEFINE(HAVE_LIBCRYPTO,1,[define whether libcrypto is installed])
> + fi
> ])
> diff --git a/testcases/kernel/security/integrity/ima/src/ima_boot_aggregate.c b/testcases/kernel/security/integrity/ima/src/ima_boot_aggregate.c
> index f67eb684b..9f500553c 100644
> --- a/testcases/kernel/security/integrity/ima/src/ima_boot_aggregate.c
> +++ b/testcases/kernel/security/integrity/ima/src/ima_boot_aggregate.c
> @@ -29,6 +29,8 @@
> #include <openssl/sha.h>
> #endif
>
> +#if HAVE_LIBCRYPTO && HAVE_OPENSSL_SHA_H
I wonder if we have to use both here, I guess that it's safer that way.
But it would be cleaner if we changed the m4 checks not to set
HAVE_LIBCRYPTO if either of the AC_CHECK_LIB() or AC_CHECK_HEADER() have
failed.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-10-09 15:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 11:00 [LTP] [RFC PATCH v2 0/7] Fix 32-bit cross compilation Petr Vorel
2017-10-09 11:00 ` [LTP] [RFC PATCH v2 1/7] m4: Fix libkeyutils detection on 32-bit cross build Petr Vorel
2017-10-09 15:06 ` Cyril Hrubis
2017-10-09 17:04 ` Petr Vorel
2017-10-09 11:00 ` [LTP] [RFC PATCH v2 2/7] m4: Fix libacl " Petr Vorel
2017-10-09 15:29 ` Cyril Hrubis
2017-10-09 11:00 ` [LTP] [RFC PATCH v2 3/7] m4: Simplify check for linux/can.h header Petr Vorel
2017-10-09 15:37 ` Cyril Hrubis
2017-10-09 11:00 ` [LTP] [RFC PATCH v2 4/7] m4: Simplify check for linux/keyctl.h header Petr Vorel
2017-10-09 11:00 ` [LTP] [RFC PATCH v2 5/7] m4: Fix libcrypto detection on 32-bit cross build Petr Vorel
2017-10-09 15:43 ` Cyril Hrubis [this message]
2017-10-09 11:01 ` [LTP] [RFC PATCH v2 6/7] make: Remove workarounds for build without libnuma Petr Vorel
2017-10-09 11:01 ` [LTP] [RFC PATCH v2 7/7] m4, kernel/lib: Detect libnuma presence in kernel libs Petr Vorel
2017-10-09 15:59 ` Cyril Hrubis
2017-10-09 17:05 ` Petr Vorel
2017-10-09 11:23 ` [LTP] [RFC PATCH v2 0/7] Fix 32-bit cross compilation Richard Palethorpe
2017-10-09 12:49 ` Petr Vorel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171009154322.GG25633@rei.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox