All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Azarewicz, PiotrX T" <piotrx.t.azarewicz@intel.com>
Cc: "Gu, YongjieX" <yongjiex.gu@intel.com>, dev@dpdk.org
Subject: Re: [PATCH] mk: fix static link with glibc < 2.17
Date: Fri, 22 Jul 2016 16:14:11 +0200	[thread overview]
Message-ID: <3192148.AlCuAgdt9y@xps13> (raw)
In-Reply-To: <4837007523CC9A4B9414D20C13DE6E64136EC4FB@IRSMSX102.ger.corp.intel.com>

2016-07-22 14:07, Azarewicz, PiotrX T:
> > > > > Tested-by: Yongjie Gu <yongjiex.gu@intel.com>
> > > >
> > > > 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?

  reply	other threads:[~2016-07-22 14:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18  9:43 [PATCH] mk: fix static link with glibc < 2.17 Thomas Monjalon
2016-07-20  1:19 ` Gu, YongjieX
2016-07-21  8:22   ` Thomas Monjalon
2016-07-22 13:38     ` Azarewicz, PiotrX T
2016-07-22 13:43       ` Thomas Monjalon
2016-07-22 14:07         ` Azarewicz, PiotrX T
2016-07-22 14:14           ` Thomas Monjalon [this message]
2016-07-22 14:47             ` Azarewicz, PiotrX T
2016-07-22 15:05               ` Thomas Monjalon
2016-07-25 11:13                 ` Azarewicz, PiotrX T
2016-07-25 12:37                   ` Thomas Monjalon
2016-07-26  7:06                     ` Azarewicz, PiotrX T

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3192148.AlCuAgdt9y@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=piotrx.t.azarewicz@intel.com \
    --cc=yongjiex.gu@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.