Bug #3544
closed./configure checks CFLAGS for jni.h if --with-hadoop is specified but also needs to check CXXFLAGS
0%
Description
If configure is used like so:
CFLAGS="-fno-omit-frame-pointer -g -O2 -I/usr/lib/jvm/java-6-openjdk-amd64/include" CXXFLAGS="-fno-omit-frame-pointer -g -O2" ./configure --with-debug --with-radosgw --with-fuse --with-tcmalloc --with-libatomic-ops --with-gtk2 --with-hadoop --with-profiler --enable-cephfs-java
then the configure checks will pass but compilation will fail on client/hadoop/CephFSInterface.h
I propose that we add checks for CXXFLAGS as well.
Updated by Noah Watkins over 11 years ago
You could probably put a AC_PUSH/POP_LANG[C++] around the JNI checks, and then configure.ac would fail properly. Currently it checks using gcc, rather than g++ which is what is used for the actual compilation.
I think this is wrong for the Java stuff, too. Instead of using CPPFLAGS, we can use CXXFLAGS as we don't have any mixing of C and C++.
Updated by Noah Watkins over 11 years ago
jni.h is also OK for C or C++. Add it CPPFLAGS to fix the problem?
Updated by Anonymous over 11 years ago
I just did a ./configure and using CPPFLAGS to indicate where the jni headers were and that worked just fine. Using CXXFLAGS results in ./configure failing because it cannot find jni.h.
Is CXXFLAGS something we want to support?
Updated by Noah Watkins over 11 years ago
I think this can be closed. There is a bunch of autoconf changes for Java that have or will be merged.
Updated by John Spray over 6 years ago
- Project changed from Ceph to CephFS
- Category changed from 20 to 48
Bulk move of hadoop category into FS project.
Updated by Patrick Donnelly about 5 years ago
- Category deleted (
48) - Labels (FS) Java/Hadoop added