From: Norbert Lange via lttng-dev <lttng-dev@lists.lttng.org>
To: Kienan Stewart <kstewart@efficios.com>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: lttng-tools-2.14.0-rc1: fails to compile with libxml2-2.14.4
Date: Tue, 17 Jun 2025 17:08:58 +0200 [thread overview]
Message-ID: <CADYdroNushrX7E3ZR8LoKLpj0rrcebPo6iJTcKBTowUWAniQYQ@mail.gmail.com> (raw)
In-Reply-To: <30d81f2c-a2ce-47b6-b999-fb6f09f1c026@efficios.com>
Am Di., 17. Juni 2025 um 16:50 Uhr schrieb Kienan Stewart
<kstewart@efficios.com>:
>
> Hi Norbert,
>
> On 6/17/25 10:15 AM, Norbert Lange via lttng-dev wrote:
> > /tmp/dev_develop_libxml2/usr/include/libxml2/libxml/encoding.h:173:7:
> > note: declared here
> > 173 | } input XML_DEPRECATED_MEMBER;
> > | ^~~~~
> > ../../../src/common/config/session-config.cpp:297:75: error: no match
> > for call to '(_xmlCharEncodingHandler::<unnamed union>) (xmlChar*&,
> > int*, const xmlChar*, int*)'
> > 297 | ret = handler->input(out_str, &out_len, (const xmlChar *)
> > in_str, &in_len);
> > |
> > ^
> >
> > Changing the call to handler->input.legacyFunc seems to fix it.
> >
> > Also lttng seems to need libxml2, but doesnt add the necessary flags.
> >
>
> Regarding the "necessary flags" for libxml2 when building the lttng
> binary, could you indicate clearly the error you have?
>
> All uses of libxml2 are via libconfig, and the libxml2 LD flags are
> added to lttng via libconfig.la.
>
> When performing the final link of lttng, I see `-lxml2` in the command line.
>
> thanks,
> kienan
> > Regards, Norbert
>
The error is, that I don't see -lxml2 in the commandline (unless I use
the global LDFLAGS), libconfig.la does not contain the flags either.
However, the Makefiles all contain them:
src/common/Makefile:libxml2_CFLAGS =
-I/tmp/dev_develop_libxml2/usr/include/libxml2
src/common/Makefile:libxml2_LIBS =
/tmp/dev_develop_libxml2/usr/local/lib/libxml2.so
I dont use pkgconf, I set the variables directly (libxml2 is not a
part of our production filesystem + compiler and right now I just
barely managed to compile lttng somehow).
Regards, Norbert
next prev parent reply other threads:[~2025-06-17 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 14:15 Norbert Lange via lttng-dev
2025-06-17 14:19 ` Kienan Stewart via lttng-dev
2025-06-17 14:50 ` Kienan Stewart via lttng-dev
2025-06-17 15:08 ` Norbert Lange via lttng-dev [this message]
2025-06-17 17:29 ` Kienan Stewart 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=CADYdroNushrX7E3ZR8LoKLpj0rrcebPo6iJTcKBTowUWAniQYQ@mail.gmail.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