From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] mk: fix static link with glibc < 2.17 Date: Fri, 22 Jul 2016 16:14:11 +0200 Message-ID: <3192148.AlCuAgdt9y@xps13> References: <1468835025-3333-1-git-send-email-thomas.monjalon@6wind.com> <1680274.k5QNW9e4Yu@xps13> <4837007523CC9A4B9414D20C13DE6E64136EC4FB@IRSMSX102.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: "Gu, YongjieX" , dev@dpdk.org To: "Azarewicz, PiotrX T" Return-path: Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48]) by dpdk.org (Postfix) with ESMTP id 9D2CD4AAD for ; Fri, 22 Jul 2016 16:14:14 +0200 (CEST) Received: by mail-wm0-f48.google.com with SMTP id f65so59226887wmi.0 for ; Fri, 22 Jul 2016 07:14:14 -0700 (PDT) In-Reply-To: <4837007523CC9A4B9414D20C13DE6E64136EC4FB@IRSMSX102.ger.corp.intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-07-22 14:07, Azarewicz, PiotrX T: > > > > > Tested-by: Yongjie Gu > > > > > > > > Applied > > > > > > OS: UB1204 > > > GCC: 4.6.4 > > > Kernel: 3.13.0-45 > > > glibc 2.15 > > > > > > x86_64-native-linuxapp-gcc: FAIL > > > > Please don't be a bot and explain us the error you see. > > I was trying rc3 + fix and latest (today) dpdk version. The same fail message: > > /x86_64-native-linuxapp-gcc/lib/librte_eal.a(eal_timer.o): In function `get_tsc_freq': > eal_timer.c:(.text+0x128): undefined reference to `clock_gettime' > eal_timer.c:(.text+0x166): undefined reference to `clock_gettime' > /x86_64-native-linuxapp-gcc/lib/librte_eal.a(eal_alarm.o): In function `eal_alarm_callback': > eal_alarm.c:(.text+0xda): undefined reference to `clock_gettime' > /x86_64-native-linuxapp-gcc/lib/librte_eal.a(eal_alarm.o): In function `rte_eal_alarm_set': > eal_alarm.c:(.text+0x211): undefined reference to `clock_gettime' Interesting. Could check the command line in verbose mode to see where is -lrt please?