All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: buildroot@buildroot.org, Thomas Devoogdt <thomas@devoogdt.com>
Subject: Re: [Buildroot] [PATCH] package/libsoup3: fix static build
Date: Mon, 28 Sep 2026 13:08:06 +0200	[thread overview]
Message-ID: <arpKendqnCAoe3mc@windsurf> (raw)
In-Reply-To: <20260927221958.864086-1-yegorslists@gmail.com>

On Mon, Sep 28, 2026 at 12:19:58AM +0200, Yegor Yefremov via buildroot wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
> 
> Since the bump to 3.7.3, libsoup unconditionally includes <dlfcn.h>
> in soup-init.c to detect whether libsoup2 is loaded in the same
> process. Static-only toolchains such as uClibc-ng without shared
> library support don't provide this header, so the build fails:
> 
> ../libsoup/soup-init.c:21:10: fatal error: dlfcn.h: No such file or directory
> 
> Add a patch, submitted upstream, that checks for dlfcn.h at configure
> time and skips the libsoup2 detection when it is not available.
> 
> Fixes:
> https://autobuild.buildroot.org/results/4effebe5fc12146749e704dd56f695363cc8fbc3
> 
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> Assisted-by: Claude:claude-opus-5

It would be even better to explicitly mention the commit that
introduced the regression, so I've added a Fixes: tag with this
information.

Applied to master, thanks!

Best regards,

Thomas Petazzoni
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-09-28 11:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-27 22:19 [Buildroot] [PATCH] package/libsoup3: fix static build Yegor Yefremov via buildroot
2026-09-28 11:08 ` Thomas Petazzoni 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=arpKendqnCAoe3mc@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=thomas@devoogdt.com \
    --cc=yegorslists@googlemail.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.