Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Bernd Kuhls <bernd@kuhls.net>,
	buildroot@buildroot.org,
	Titouan Christophe <titouan.christophe@mind.be>
Subject: Re: [Buildroot] [PATCH v2 1/1] package/asterisk: security bump version to 22.5.2
Date: Sat, 10 Jan 2026 12:46:18 +0100	[thread overview]
Message-ID: <aWI8CmIeP5d57VKp@waldemar-brodkorb.de> (raw)
In-Reply-To: <20251209093955.75fc0716@windsurf>

Hi Thomas,
Thomas Petazzoni via buildroot wrote,

> Hello Bernd,
> 
> On Thu,  6 Nov 2025 21:47:37 +0100
> Bernd Kuhls <bernd@kuhls.net> wrote:
> 
> > Fixes CVE-2025-1131:
> > https://github.com/asterisk/asterisk/security/advisories/GHSA-v9q8-9j8m-5xwp
> > 
> > Acked-by: Titouan Christophe <titouan.christophe@mind.be>
> > Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> 
> I'm not sure it's been introduced by this version bump, but Asterisk is
> still causing quite a few build failures in the autobuilders.
> 
> I briefly looked into two of them:
> 
> - https://autobuild.buildroot.net/results/426/426336052c50768b06dd047ce4b8283e6da377d4/build-end.log
> 
>   menuselect/menuselect: error while loading shared libraries: libxml2.so.16: cannot open shared object file: No such file or directory
> 
>   The target asterisk package builds "menuselect" as a host tool, but
>   our $(HOST_LDFLAGS) are not passed when building menuselect, so it
>   doesn't have the right -Wl,-rpath flag passed, and therefore when it
>   tries to *run* menuselect, it doesn't find libxml2 in $(HOST_DIR)/lib
> 
>   Not sure how to pass our HOST_LDFLAGS.
> 
>   Also, since it builds menuselect for the host, is it still needed for
>   the target asterisk to depend on host-asterisk ?

The problem here is that somehow newer versions of Asterisk do
trigger sometimes a make clean before the build and then our
host-asterisk mechanism is useless, because menuselect is build
again without our HOST_LDFLAGS. I can reproduce the issue and have a
ugly one-liner patch preventing the cleanup.

Should I sent a patch?

best regards
 Waldemar
 
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-01-10 11:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06 20:47 [Buildroot] [PATCH v2 1/1] package/asterisk: security bump version to 22.5.2 Bernd Kuhls
2025-11-12 20:44 ` Peter Korsgaard
2025-11-27 19:53 ` Arnout Vandecappelle via buildroot
2025-12-09  8:39 ` Thomas Petazzoni via buildroot
2026-01-10 11:46   ` Waldemar Brodkorb [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=aWI8CmIeP5d57VKp@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --cc=bernd@kuhls.net \
    --cc=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=titouan.christophe@mind.be \
    /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