All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/fluidsynth: fix download-while-configure since 2.5.7 bump
Date: Fri, 28 Aug 2026 11:35:26 +0200	[thread overview]
Message-ID: <a133e2db4d8f6dc6405a1907705a07aa@free.fr> (raw)
In-Reply-To: <20260827081626.1018466-1-thomas.petazzoni@bootlin.com>

On 27/08/2026 10:16, Thomas Petazzoni via buildroot wrote:
> Since commit
> 566bdcb97f5706aa08f40a88e4728e4a0bed8257 ("package/fluidsynth:
> security bump to version 2.5.7"), fluidsynth tries to download some
> "gcem" code during its configure step, which not only violates
> Buildroot's policies, but also breaks the build if network is not
> available during the build.
> 
> To fix this, we add an EXTRA_DOWNLOADS to grab gcem and extract it at
> the right place. Some minor fix (submitted upstream) is needed to
> ensure the FindGCEM.cmake logic properly finds that gcem is already in
> the source tree.
> 
> Fixes:
> 
>   
> https://autobuild.buildroot.net/results/048df28f6ab97a16731e62d7f56c6eba565cda63/
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Applied to master, thanks for catching this issue!

Best regards,

Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-08-28  9:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27  8:16 [Buildroot] [PATCH v2] package/fluidsynth: fix download-while-configure since 2.5.7 bump Thomas Petazzoni via buildroot
2026-08-28  9:35 ` Julien Olivain via buildroot [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=a133e2db4d8f6dc6405a1907705a07aa@free.fr \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.