Bugzilla – Bug 137009
make error when compile ocfs2 tools from source
Last modified: 2005-12-07 09:15:07 UTC
Hi The problem occurs when I try to install ocfs2 tools from source (1.1.2). Machine runs SuSE 10. Gcc version is 4.0.2. Kernel is 2.6.13-15. OCFS2 is 1.1.6 Installed are: e2fsprogs-1.38-4 and e2fsprogs-devel-1.38-4 Thank you. Ivo =========================================================================== make -C fsck.ocfs2 make[1]: Entering directory `/usr/src/ocfs2-tools-1.1.2/fsck.ocfs2' gcc -ggdb -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -static -o fsck.ocfs2 fsck.o dirblocks.o dirparents.o extent.o icount.o journal.o pass0.o pass1.o pass2.o pass3.o pass4.o problem.o strings.o util.o ../libocfs2/libocfs2.a ../libo2dlm/libo2dlm.a ../libo2cb/libo2cb.a -L../libocfs2 -locfs2 -L../libo2dlm -lo2dlm -L../libo2cb -lo2cb -lcom_err /usr/lib/gcc/i586-suse-linux/4.0.2/../../../libcom_err.a(error_message.o): In function `et_list_lock': : undefined reference to `pthread_mutex_lock' /usr/lib/gcc/i586-suse-linux/4.0.2/../../../libcom_err.a(error_message.o): In function `et_list_unlock': : undefined reference to `pthread_mutex_unlock' collect2: ld returned 1 exit status make[1]: *** [fsck.ocfs2] Error 1 make[1]: Leaving directory `/usr/src/ocfs2-tools-1.1.2/fsck.ocfs2' make: *** [fsck.ocfs2] Error 2 ================================================================================ Logged a bug with Oracle and their responce is: ------- Additional Comment #1 From Joel Becker 2005-11-03 22:03 [reply] ------- Wow, a threaded libcom_err seems a bit wacky. But I guess we'll have to handle it. Thanks for reporting. ------- Additional Comment #2 From paul_taysom@novell.com 2005-11-16 09:47 [reply] ------- Just needs the "-lpthread" library. ------- Additional Comment #3 From Joel Becker 2005-11-16 10:02 [reply] ------- Right. The bug is that it needs the -lpthread library. We've filed with SuSE a while back about this, as libcom_err should not be requiring -lpthread.
Why libcom_err needs this is explained in Bug #66534
Nice. I can't access bug 66534.] (In reply to comment #1) > Why libcom_err needs this is explained in Bug #66534 >
sorry try again...