All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: tglx@linutronix.de
Cc: linux-rt-users@vger.kernel.org
Subject: Re: cyclictest hangs with posix interval timers !?
Date: Mon, 08 Jan 2007 11:10:16 +0100	[thread overview]
Message-ID: <45A21888.8060702@imc-berlin.de> (raw)
In-Reply-To: <1167986882.23138.52.camel@localhost.localdomain>

Thomas,

> This looks like a serious problem with your cross compiler / glibc
> setup. Can you compile cyclictest on one of your desktop machines and
> link it statically ?

As I wrote I have problems linking it statically!

 gcc -Wall -O2  -lpthread -lrt cyclictest.c -o cyclictest -static

results in

/tmp/cc30ryGd.o: In function `main':
cyclictest.c:(.text+0x4a2): undefined reference to `pthread_create'
cyclictest.c:(.text+0x6d9): undefined reference to `pthread_kill'
cyclictest.c:(.text+0x6f0): undefined reference to `pthread_join'
/tmp/cc30ryGd.o: In function `timerthread':
cyclictest.c:(.text+0x839): undefined reference to `clock_gettime'
cyclictest.c:(.text+0x881): undefined reference to `timer_settime'
cyclictest.c:(.text+0x90c): undefined reference to `clock_gettime'
cyclictest.c:(.text+0xa7b): undefined reference to `clock_gettime'
cyclictest.c:(.text+0xa8c): undefined reference to `clock_nanosleep'
cyclictest.c:(.text+0xb08): undefined reference to `timer_delete'
cyclictest.c:(.text+0xb79): undefined reference to `clock_gettime'
cyclictest.c:(.text+0xbd8): undefined reference to `clock_nanosleep'
cyclictest.c:(.text+0xc37): undefined reference to `timer_create'
collect2: ld returned 1 exit status

while

 gcc -Wall -O2 cyclictest.c -o cyclictest -lrt -lpthread -static

compiles and links fine!

Any idea why the order matters?

--
Steven

  parent reply	other threads:[~2007-01-08 10:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04 11:43 cyclictest hangs with posix interval timers !? Steven Scholz
2007-01-04 11:52 ` Robert Schwebel
2007-01-04 12:08   ` Steven Scholz
2007-01-04 13:15   ` Steven Scholz
2007-01-04 13:27     ` Thomas Gleixner
2007-01-04 13:31       ` Steven Scholz
2007-01-04 13:47         ` Thomas Gleixner
2007-01-04 15:01       ` Steven Scholz
2007-01-05  8:48         ` Thomas Gleixner
2007-01-05  9:16           ` Robert Schwebel
2007-01-07 12:38           ` Steven Scholz
2007-01-07 12:51           ` Steven Scholz
2007-01-07 14:21             ` Thomas Gleixner
2007-01-07 14:38               ` Steven Scholz
2007-01-07 14:52                 ` Thomas Gleixner
2007-01-07 14:55                   ` Steven Scholz
2007-01-07 15:32                   ` Steven Scholz
2007-01-08 10:10           ` Steven Scholz [this message]
2007-01-08 10:28             ` Robert Schwebel
2007-01-08 11:37           ` Steven Scholz
2007-01-08 11:42             ` Robert Schwebel
2007-01-08 11:43               ` Steven Scholz
2007-01-04 13:30 ` Thomas Gleixner
2007-01-04 13:32   ` Steven Scholz

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=45A21888.8060702@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.