[
https://issues.apache.org/jira/browse/HDFS-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492905#comment-13492905
]
Colin Patrick McCabe commented on HDFS-4164:
--------------------------------------------
The build failure looks like this:
{code}
23:43:12 [exec] /usr/bin/gcc -g -Wall -O2 -D_GNU_SOURCE
-D_REENTRANT -D_FILE_OFFSET_BITS=64 -D_FILE_OFFSET_BITS=64
-I/usr/include/fuse CMakeFiles/fuse_dfs.dir/fuse_dfs.c.o
CMakeFiles/fuse_dfs.dir/fuse_options.c.o
CMakeFiles/fuse_dfs.dir/fuse_connect.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_access.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_chmod.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_chown.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_create.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_flush.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_getattr.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_mkdir.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_mknod.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_open.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_read.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_readdir.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_release.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_rename.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_rmdir.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_statfs.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_symlink.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_truncate.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_unlink.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_utimens.c.o
CMakeFiles/fuse_dfs.dir/fuse_impls_write.c.o
CMakeFiles/fuse_dfs.dir/fuse_init.c.o
CMakeFiles/fuse_dfs.dir/fuse_stat_struct.c.o
CMakeFiles/fuse_dfs.dir/fuse_trash.c.o
CMakeFiles/fuse_dfs.dir/fuse_users.c.o -o fuse_dfs -rdynamic -lfuse
/mnt/jenkins/toolchain/JDK6u20-64bit/jre/lib/amd64/server/libjvm.so
../../../target/usr/local/lib/libhdfs.so.0.0.0 -lm -lpthread
/mnt/jenkins/toolchain/JDK6u20-64bit/jre/lib/amd64/server/libjvm.so
-Wl,-rpath,/mnt/jenkins/toolchain/JDK6u20-64bit/jre/lib/amd64/server:/mnt/jenkins/workspace/Bigtop-trunk-Hadoop/label/opensuse12/build/hadoop/rpm/BUILD/hadoop-2.0.2-alpha-src/hadoop-hdfs-project/hadoop-hdfs/target/native/target/usr/local/lib
23:43:12 [exec] make[3]: Leaving directory
`/mnt/jenkins/workspace/Bigtop-trunk-Hadoop/label/opensuse12/build/hadoop/rpm/BUILD/hadoop-2.0.2-alpha-src/hadoop-hdfs-project/hadoop-hdfs/target/native'
23:43:12 [exec] make[2]: Leaving directory
`/mnt/jenkins/workspace/Bigtop-trunk-Hadoop/label/opensuse12/build/hadoop/rpm/BUILD/hadoop-2.0.2-alpha-src/hadoop-hdfs-project/hadoop-hdfs/target/native'
23:43:12 [exec] make[1]: Leaving directory
`/mnt/jenkins/workspace/Bigtop-trunk-Hadoop/label/opensuse12/build/hadoop/rpm/BUILD/hadoop-2.0.2-alpha-src/hadoop-hdfs-project/hadoop-hdfs/target/native'
23:43:13 [exec]
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-linux/bin/ld:
CMakeFiles/fuse_dfs.dir/fuse_connect.c.o: undefined reference to
symbol 'clock_gettime@@GLIBC_2.2.5'
23:43:13 [exec]
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-linux/bin/ld:
note: 'clock_gettime@@GLIBC_2.2.5' is defined in DSO /lib64/librt.so.1
so try adding it to the linker command line
23:43:13 [exec] /lib64/librt.so.1: could not read symbols:
Invalid operation
23:43:13 [exec] collect2: error: ld returned 1 exit status
23:43:13 [exec] make[3]: *** [main/native/fuse-dfs/fuse_dfs] Error 1
23:43:13 [exec] make[2]: ***
[main/native/fuse-dfs/CMakeFiles/fuse_dfs.dir/all] Error 2
23:43:13 [exec] make[1]: *** [all] Error 2
{code}
I haven't personally confirmed the fix yet, but confirmation should be coming
soon.
> fuse_dfs: add -lrt to the compiler command line on Linux
> --------------------------------------------------------
>
> Key: HDFS-4164
> URL: https://issues.apache.org/jira/browse/HDFS-4164
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: fuse-dfs
> Affects Versions: 2.0.3-alpha
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Priority: Minor
> Attachments: HDFS-4164.001.patch
>
>
> We need to add -ltr to the compiler command line on Linux in order to use
> clock_gettime on OpenSuSE 12.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
