Bug #503
closedmake of lttng-tools 2.2.0-rc1 fails with undefined reference to symbol 'timer_settime@@GLIBC_2.3.3'
0%
Description
Using the latest 2.2.0-rc1 suite, since the gold
linker is no longer listed as required by the lttng-tools README
, I removed it (removed the binutils-gold
package) to revert to the default linker, and then tried to rebuild lttng-tools
. To my surprise, it failed with "undefined reference to symbol 'timer_settime@@GLIBC_2.3.3'
". Stranger yet, rebuilding it with LDFLAGS=-L/usr/local/lib
passed to the configure
call fixed the problem. My understanding was that the gold
linker needed LDFLAGS=-L/usr/local/lib
in the configure
because it ignored ld.so.conf
, so the default linker should not have the same problem.
The build is:
./bootstrap &> bootstrap.log ./configure --enable-python-bindings &> configure.log ./make &> make.log
The failure is:
[...] Making all in lttng-consumerd make[3]: Entering directory `/home/daniel/Documents/lttng-tools-dec56f6/src/bin/lttng-consumerd' CC lttng-consumerd.o CCLD lttng-consumerd /usr/bin/ld: ../../../src/common/.libs/libconsumer.a(consumer-timer.o): undefined reference to symbol 'timer_settime@@GLIBC_2.3.3' /usr/bin/ld: note: 'timer_settime@@GLIBC_2.3.3' is defined in DSO /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/librt.so so try adding it to the linker command line /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/librt.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [lttng-consumerd] Error 1 make[3]: Leaving directory `/home/daniel/Documents/lttng-tools-dec56f6/src/bin/lttng-consumerd' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/daniel/Documents/lttng-tools-dec56f6/src/bin' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/daniel/Documents/lttng-tools-dec56f6/src' make: *** [all-recursive] Error 1
The logs are attached.
Files
Updated by David Goulet over 11 years ago
- Status changed from New to Resolved
- Assignee set to David Goulet
This should be fixed with commit id "4e8fa55be8937805621fad9ff289e5affc2ef71b" of master.
I'm changing this ticket to Resolved. If not, we'll reopened it.