Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: Norbert Lange <nolange79@gmail.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: lttng-tools-2.14.0-rc1: Not possible to disable babeltrace2 dependency
Date: Tue, 17 Jun 2025 14:28:45 -0400	[thread overview]
Message-ID: <9ebcf017-6276-4465-9ef0-27ea005d9106@efficios.com> (raw)
In-Reply-To: <CADYdroPaw5bMAinD203xd3mOO001izA==UDu+C1Jso32jFAEOQ@mail.gmail.com>

Hi Norbert,

thanks for the reporting this issue! I've proposed a patch[1] to handle 
the case you've described.

thanks,
kienan

[1]: https://review.lttng.org/c/lttng-tools/+/14829

On 6/17/25 10:18 AM, Norbert Lange wrote:
> Am Di., 17. Juni 2025 um 16:13 Uhr schrieb Kienan Stewart via
> lttng-dev <lttng-dev@lists.lttng.org>:
>>
>> Hi Norbert,
>>
>> could you describe more about the context of the system you were
>> building on, and which version of babeltrace you had installed?
>>
>> thanks,
>> kienan
>>
>> On 6/17/25 6:54 AM, Norbert Lange via lttng-dev wrote:
>>> Hello,
>>>
>>> I had to add babeltrace2_CFLAGS="-DA" babeltrace2_LIBS="-lm" to the
>>> configure line
>>> to be able to build.
>>>
>>> There should be a --without-babeltrace2 switch and possible automatic detection.
>>>
>>> Regards, Norbert
> 
> Its a crosstool-ng toolchain based on gcc 10.5.
> There is NO babeltrace2 available, and that is what is not handled, I
> have to define babeltrace2_CFLAGS and babeltrace2_LIBS to make it
> through the checks.
> 
> Regards, Norbert


      reply	other threads:[~2025-06-17 18:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17 10:54 Norbert Lange via lttng-dev
2025-06-17 14:13 ` Kienan Stewart via lttng-dev
2025-06-17 14:18   ` Norbert Lange via lttng-dev
2025-06-17 18:28     ` Kienan Stewart via lttng-dev [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=9ebcf017-6276-4465-9ef0-27ea005d9106@efficios.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=kstewart@efficios.com \
    --cc=nolange79@gmail.com \
    /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