dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Török Edwin" <edwintorok@gmail.com>
To: Julien Cristau <jcristau@debian.org>
Cc: dri-devel@lists.sourceforge.net
Subject: Re: [PATCH] tests/ programs need -lrt too since they use clock_gettime.
Date: Fri, 09 Apr 2010 22:09:23 +0300	[thread overview]
Message-ID: <4BBF7B63.2070000@gmail.com> (raw)
In-Reply-To: <20100409190049.GK3082@radis.liafa.jussieu.fr>

On 04/09/2010 10:00 PM, Julien Cristau wrote:
> On Fri, Apr  9, 2010 at 16:46:46 +0300, Török Edwin wrote:
>
>> When using the binutils gold linker, even if libdrm.so is already linked against
>> -lrt you still need to link your app against -lrt if your app needs symbols from
>> it.
>>
>> Signed-off-by: Török Edwin<edwintorok@gmail.com>
>> ---
>>   tests/Makefile.am |    2 +-
>>   1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/tests/Makefile.am b/tests/Makefile.am
>> index 3e74705..81006ab 100644
>> --- a/tests/Makefile.am
>> +++ b/tests/Makefile.am
>> @@ -4,7 +4,7 @@ AM_CPPFLAGS = \
>>   	-I $(top_srcdir)/include/drm \
>>   	-I $(top_srcdir)
>>
>> -LDADD = $(top_builddir)/libdrm.la
>> +LDADD = $(top_builddir)/libdrm.la @CLOCK_LIB@
>>
>>   noinst_PROGRAMS = \
>>   	dristat \
>
> The tests don't use librt afaict, the uses of clock_gettime() are in
> libdrm and libdrm_intel.  So your explanation doesn't seem to make
> sense...

The test app links dristat.o, and that includes xf86drm.c that uses 
clock_gettime.

Here is the link error I get without my patch:
make[1]: Entering directory `/home/edwin/drm/tests
libtool: link: gcc -m32 -O2 -g -o .libs/dristat dristat.o 
../.libs/libdrm.so
/usr/bin/ld: dristat.o: in function drmWaitVBlank:../xf86drm.c:1930: 
error: undefined reference to 'clock_gettime'
/usr/bin/ld: dristat.o: in function drmWaitVBlank:../xf86drm.c:1941: 
error: undefined reference to 'clock_gettime'
collect2: ld returned 1 exit status

dristat.c is including xf86drm.c directly (no idea why, shouldn't it get 
what it needs from libdrm.so?):
#include "xf86drm.c"

And xf86drm.c uses clock_gettime:
xf86drm.c:    ret = clock_gettime(CLOCK_MONOTONIC, &timeout);
xf86drm.c:      fprintf(stderr, "clock_gettime failed: %s\n", 
strerror(ret));
xf86drm.c:             clock_gettime(CLOCK_MONOTONIC, &cur);


Best regards,
--Edwin

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--

      reply	other threads:[~2010-04-09 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09 13:46 [PATCH] tests/ programs need -lrt too since they use clock_gettime Török Edwin
2010-04-09 19:00 ` Julien Cristau
2010-04-09 19:09   ` Török Edwin [this message]

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=4BBF7B63.2070000@gmail.com \
    --to=edwintorok@gmail.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=jcristau@debian.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox