lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: MONTET Julien via lttng-dev <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] LTTng 32 bits : Cannot find liburcu-bp 0.11 or newer
Date: Mon, 29 Mar 2021 09:43:42 +0000	[thread overview]
Message-ID: <PR3PR02MB62022F27BFAE30836B7E094ED17E9@PR3PR02MB6202.eurprd02.prod.outlook.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 851 bytes --]

Hi everyone,

I successfully installed and used LTTng on x86 and x64 (kernel event, userspace, and other tools like TraceCompass).

Now, I am looking for a way to use LTTng on other processors (arm32, ...).

I tried to follow the tutorial and, to be honest, I am quite not lost on step 2. (libuuid, popt, libxml2)
https://lttng.org/docs/v2.12/#doc-instrumenting-32-bit-app-on-64-bit-system

My current issue is on the step 3.
During the installation (./configure), I have the following error :
error: Cannot find liburcu-bp 0.11 or newer. Use LDFLAGS=-Ldir to specify its location.

This file - liburcu - is in /usr/local/lib32 : Ubuntu Pastebin<https://paste.ubuntu.com/p/b67Bxf6cfB/>

This topic was started a long time ago here :
https://lists.lttng.org/pipermail/lttng-dev/2013-February/019641.html

Would you mind helping me ?

[-- Attachment #1.2: Type: text/html, Size: 4334 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

             reply	other threads:[~2021-03-29  9:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29  9:43 MONTET Julien via lttng-dev [this message]
2021-03-29 13:24 ` [lttng-dev] LTTng 32 bits : Cannot find liburcu-bp 0.11 or newer MONTET Julien via lttng-dev
2021-03-29 13:51   ` Jonathan Rajotte-Julien via lttng-dev

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=PR3PR02MB62022F27BFAE30836B7E094ED17E9@PR3PR02MB6202.eurprd02.prod.outlook.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=julien.montet@reseau.eseo.fr \
    /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;
as well as URLs for NNTP newsgroup(s).