This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
libc version librt and timer_create timer_delete
- From: "Timm Baumeister" <siriustorrent at gmail dot com>
- To: libc-help at sourceware dot org
- Date: Tue, 22 Jul 2008 14:23:41 -0400
- Subject: libc version librt and timer_create timer_delete
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=Rxi344/MZXM7G+zjVxEDlETO5wMCib0SnMMlsyLgr8g=; b=A24qHDzQ1nMZ4Axs5dyqXujufQzz/80Rl7JZK4LESnwV6okQKtw9dma+Ol/xxqGC+5 vzomgrb2/dxgnNFXQoFr0LwphHhd7vjHfeNxldC5UrMSaUk/cNBTSo8Cwfzk7hGHQ5HX xRzYC7bNA594H3EfhsmgjgPQizl6KbB/Eh5dU=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=CPbTAuKgl2Ew2ddvhHwZNcRDBa32Q8oSvbZ+RKkA68+7/5ptD3FC/Uby0g7zJObQwC SXPKFyauzZuR6gqkhuRhozWHIqhKx4+aabcHUf1YJvP+YXnhw3PmxNn/DchcLa7C/SOq 0TQTMRZ848qhy2lXgxPwyM2ACsg5DZn2EZznM=
Hi,
While trying to build a program which has a link dependency to a third
party library (libScaleViz.so) I get the following linker errors:
../../../product/lib/arch-LinuxAMD64-Debug/libScaleViz.so: undefined
reference to `timer_delete@GLIBC_2.3.3'
../../../product/lib/arch-LinuxAMD64-Debug/libScaleViz.so: undefined
reference to `timer_create@GLIBC_2.3.3'
../../../product/lib/arch-LinuxAMD64-Debug/libScaleViz.so: undefined
reference to `timer_settime@GLIBC_2.3.3'
libScaleViz has among others the following dependency:
libc.so.6 => /lib64/tls/libc.so.6 (0x0000002a95a88000)
librt.so.1 => /lib64/tls/librt.so.1 (0x0000002a9586000)
Looking at this library with
objdump -x /lib64/tls/libc.so.6 |grep timer
confirms that these symbols indeed do not exist. They do, however,
exist in /lib64/tls/librt.so.1
My system is Centos 4.6 which is equivalent to RHEL 4U6. glibc is
libc-2.3.4.so, gcc 4.1.2
I am wondering how this problem could occur in the first place. The
version of glibc against which the library was linked contained these
symbols. Is this a glitch in the backward compatibility of glibc? And
can someone tell me how to fix this or do I need a different system
with glibc 2.3.3. to do the build?
Thanks in advance for help
Timm