Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Daniel.Thibault@drdc-rddc.gc.ca (Thibault, Daniel)
Subject: [lttng-dev] liburcu error: Cannot find -lurcu
Date: Fri, 22 Nov 2013 15:46:15 +0000	[thread overview]
Message-ID: <48CF5AC71E61DB46B70D0F388054EFFD267A58A5@VAL-E-01.valcartier.drdc-rddc.gc.ca> (raw)

> I edited the log to show only the error. The detailed log is  :

   Copy-writer's tip: when omitting irrelevant parts from a log (or conversation quote), indicate the omission with an ellipsis (e.g. '(...)' or '[...]').

> $ make
> make  all-recursive
> [...]
>  CC     wfstack.lo
>  CCLD   liburcu-common.la
>  CC     urcu.lo

   That's the line that creates liburcu.so.  It seems to succeed, albeit with a number of warnings.

> In file included from urcu.c:530:
> urcu-call-rcu-impl.h: In function 'alloc_cpu_call_rcu_data':
> urcu-call-rcu-impl.h:150: warning: implicit declaration of function 'rpl_malloc'
> urcu-call-rcu-impl.h:150: warning: assignment makes pointer from integer without a cast
> [...]
>  CC     urcu-pointer.lo
> [...]
> make -f Makefile.cds_hlist_add_head_rcu
> make[6]: Entering directory
> `/home/kumar/userspace/userspace-rcu/doc/examples/hlist'
> cc  -g -O2 -Wall -I../../../urcu/ -I../../../ -g -O2 \
>        -c -o cds_hlist_add_head_rcu.o cds_hlist_add_head_rcu.c cc -g -O2 -Wall  -g -O2 -L../../../.libs/ -Wl,-rpath="/home/kumar/userspace/userspace-rcu/doc/examples/../../.libs/" \
>        -o cds_hlist_add_head_rcu cds_hlist_add_head_rcu.o -lurcu
> /usr/bin/ld: skipping incompatible ../../../.libs//liburcu.so when searching for -lurcu

   But when we get here and try to use liburcu.so for the first time, it turns out to be "incompatible".

> /usr/bin/ld: skipping incompatible ../../../.libs//liburcu.a when searching for -lurcu
> /usr/bin/ld: cannot find -lurcu
> collect2: ld returned 1 exit status
> make[6]: *** [cds_hlist_add_head_rcu] Error 1
> [...]

   Except for the warnings, your make log matches mine up to the fatal liburcu.so incompatibility error.

   Could the compiler be misconfigured?  Try making a small test .so and application pair.

Daniel U. Thibault
Protection des syst?mes et contremesures (PSC) | Systems Protection & Countermeasures (SPC)
Cyber s?curit? pour les missions essentielles (CME) | Mission Critical Cyber Security (MCCS)
R & D pour la d?fense Canada - Valcartier (RDDC Valcartier) | Defence R&D Canada - Valcartier (DRDC Valcartier)
2459 route de la Bravoure
Qu?bec QC  G3J 1X5
CANADA
Vox : (418) 844-4000 x4245
Fax : (418) 844-4538
NAC : 918V QSDJ <http://www.travelgis.com/map.asp?addr=918V%20QSDJ>
Gouvernement du Canada | Government of Canada
<http://www.valcartier.drdc-rddc.gc.ca/>



             reply	other threads:[~2013-11-22 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22 15:46 Thibault, Daniel [this message]
     [not found] ` <CAO_Arvo3AHW3bqWtMJXb_YExCyvyCjqSaA-CfBJL=upPV+7jyw@mail.gmail.com>
2013-11-25  6:41   ` [lttng-dev] Fwd: " kumar s
  -- strict thread matches above, loose matches on Subject: below --
2013-11-22 13:57 [lttng-dev] " Thibault, Daniel
2013-11-22 14:59 ` kumar s
2013-11-22  5:21 kumar s

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=48CF5AC71E61DB46B70D0F388054EFFD267A58A5@VAL-E-01.valcartier.drdc-rddc.gc.ca \
    --to=daniel.thibault@drdc-rddc.gc.ca \
    /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