From 04cb735f44e30bc7bdde1d857ba27e1654c6415b Mon Sep 17 00:00:00 2001 From: Nico Kruber Date: Mon, 29 Jul 2019 15:37:41 +0200 Subject: [PATCH] Fix native-build/target/lib wanted but build in native-build/target/lib64 Motivation: On openSUSE (probably more), 64 bit builds use lib64, e.g. /usr/lib64, and configure picks this up and builds the native library in native-build/target/lib64 where maven is not looking. Modifications: Explicitly specify --libdir=${project.build.directory}/native-build/target/lib during configuration. Result: Maven uses the correct lib directory. --- transport-native-epoll/pom.xml | 1 + transport-native-kqueue/pom.xml | 1 + 2 files changed, 2 insertions(+) diff --git a/transport-native-epoll/pom.xml b/transport-native-epoll/pom.xml index 09c4d3b8970..d9b46e6c707 100644 --- a/transport-native-epoll/pom.xml +++ b/transport-native-epoll/pom.xml @@ -155,6 +155,7 @@ ${jni.compiler.args.ldflags} ${jni.compiler.args.cflags} + --libdir=${project.build.directory}/native-build/target/lib diff --git a/transport-native-kqueue/pom.xml b/transport-native-kqueue/pom.xml index 1bddd4f492a..1a0d49434d0 100644 --- a/transport-native-kqueue/pom.xml +++ b/transport-native-kqueue/pom.xml @@ -84,6 +84,7 @@ explicitly set the target platform. Otherwise we may get fatal link errors due to weakly linked methods which are not expected to be present on MacOS (e.g. accept4). --> MACOSX_DEPLOYMENT_TARGET=10.6 + --libdir=${project.build.directory}/native-build/target/lib