All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Buildbot cannot compile xenoma: rtcanconfig refences pthread_kill
Date: Tue, 15 Aug 2006 13:55:20 +0200	[thread overview]
Message-ID: <1155642921.4327.7.camel@domain.hid> (raw)
In-Reply-To: <44E182B8.8000300@domain.hid>

On Tue, 2006-08-15 at 10:15 +0200, Jan Kiszka wrote:
> Niklaus Giger wrote:
> > Hi
> > 
> > All my PPC based compilation fail with something like
> > 
> > ccache gcc -rdynamic -o .libs/rtcanconfig 
> > rtcanconfig.o  -L/mnt/data.ng/buildslave/buildbot/quick-ppc/build/ppc/src/skins/native -L/mnt/data.ng/buildslave/buildbot/quick-ppc/build/ppc/src/skins/rtdm /mnt/data.ng/buildslave/buildbot/quick-ppc/build/ppc/src/skins/rtdm/.libs/librtdm.so -Wl,--rpath -Wl,/usr/xenomai/lib
> > /mnt/data.ng/buildslave/buildbot/quick-ppc/build/ppc/src/skins/rtdm/.libs/librtdm.so: 
> > undefined reference to `pthread_kill'
> > http://ngiger.dyndns.org/buildbot/ppc/builds/229/step-mk_xeno/0
> > Is this only a PPC problem? It appears first with build 226, which referred to 
> > revisions 1433 and 1434. Details see 
> > http://ngiger.dyndns.org/buildbot/ppc/builds/226
> > 
> > Jan, could you please have a look at the error, as it seems to me that you 
> > reduced the lib dependencies a little bit too much?
> 
> Well, neither rtcanconfig nor librtdm have explicit dependencies on
> libpthread. Unfortunately, the generic skin init code now drags in
> pthread_kill when the linker fails to remove xeno_handle_mlock_alert for
> librtdm. That doesn't happen with my gcc-4.1, likely older compilers are
> less smart.
> 
> Anyone any ideas how to solve it WITHOUT adding -lpthread to librtdm?

Could you develop a bit more, i.e. what's the issue with adding this
dependency?

>  I
> would say either move that functions to a separate module

The reason to have this code in nucleus/bind.h is that we don't have any
dependency on common libs aside of the ones providing the skin syscalls,
and we try to avoid code duplication by not implementing this stuff into
each and every init.c files.

>  or include it
> via a separate header that all skins include except rtdm.
> 

I'm still reluctant to make RTDM an exception to the common rule,
especially to fix a compiler issue.

> > 
> > Jan BTW, I also switched the RTNet svn to the new location. 
> 
> Looking forward to the build results once we get xenomai compiling
> again. A lot of stuff changed or got added recently.
> 
> > 
> > Best regards
> > 
> 
> Jan
> 
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core
-- 
Philippe.




  reply	other threads:[~2006-08-15 11:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15  7:49 [Xenomai-core] Buildbot cannot compile xenoma: rtcanconfig refences pthread_kill Niklaus Giger
2006-08-15  8:15 ` Jan Kiszka
2006-08-15 11:55   ` Philippe Gerum [this message]
2006-08-15 12:20     ` Jan Kiszka
2006-08-15 13:44       ` Philippe Gerum
2006-08-15 18:14 ` Jan Kiszka
2006-08-15 18:56   ` Niklaus Giger
2006-08-15 19:46     ` Jan Kiszka
2006-08-15 21:29     ` Philippe Gerum
2006-08-16 13:23     ` Gilles Chanteperdrix
2006-08-16 17:37       ` Niklaus Giger

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=1155642921.4327.7.camel@domain.hid \
    --to=rpm@xenomai.org \
    --cc=jan.kiszka@domain.hid \
    --cc=xenomai@xenomai.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 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.