From 501a92dc71013d56241a4a9408d86a8a7f74cd20 Mon Sep 17 00:00:00 2001 From: Bob Glossman Date: Wed, 29 Jan 2014 12:00:42 -0800 Subject: [PATCH] LU-4470 build: wrong linux symbol file search Long standing build flaw just discovered. The autoconf function LB_CHECK_SYMBOL_EXPORT looks for the linux symbol table in the wrong place. In most builds this doesn't matter as the wrong path being used exactly matches the correct path. In SLES builds it does matter a lot. Failing to find the linux symbol table can lead to incorrect autoconf results. Change-Id: I9068f2b9aace740b67d88598844c0b8fc1d95b49 Signed-off-by: Bob Glossman Reviewed-on: http://review.whamcloud.com/9288 Tested-by: Jenkins Reviewed-by: Dmitry Eremin Tested-by: Maloo Reviewed-by: Oleg Drokin --- config/lustre-build-linux.m4 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/lustre-build-linux.m4 b/config/lustre-build-linux.m4 index eb5826b..65978fe 100644 --- a/config/lustre-build-linux.m4 +++ b/config/lustre-build-linux.m4 @@ -644,7 +644,7 @@ LB_CONFIG_OFED_BACKPORTS # or check AC_DEFUN([LB_CHECK_SYMBOL_EXPORT], [AC_MSG_CHECKING([if Linux was built with symbol $1 exported]) -grep -q -E '[[[:space:]]]$1[[[:space:]]]' $LINUX/$SYMVERFILE 2>/dev/null +grep -q -E '[[[:space:]]]$1[[[:space:]]]' $LINUX_OBJ/$SYMVERFILE 2>/dev/null rc=$? if test $rc -ne 0; then export=0 -- 1.8.3.1