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, Adrian Perez de Castro <aperez@igalia.com>
Subject: Re: [Buildroot] [PATCH] package/sysprof: propagate ucontext-related dependency from libdex
Date: Tue, 15 Sep 2026 19:22:38 +0200	[thread overview]
Message-ID: <58bcdc3c74bd0df31763ec3708cd01ae@free.fr> (raw)
In-Reply-To: <20260914213922.1847792-1-thomas.petazzoni@bootlin.com>

On 14/09/2026 23:39, Thomas Petazzoni via buildroot wrote:
> BR2_PACKAGE_SYSPROF selects BR2_PACKAGE_LIBDEX but did not propagate:
> 
> 	depends on BR2_TOOLCHAIN_HAS_UCONTEXT || \
> 		BR2_PACKAGE_LIBUCONTEXT_ARCH_SUPPORTS
> 
> from libdex. This commit fixes this missing dependency. In terms of
> Config.in comment, we do the same as what libdex is doing: handle it
> as a toolchain dependency (rather than an architecture dependency).
> 
> This was missed in commit a73ef093f7b40297d69c6813c44fd4626883632e,
> which added the ucontext related dependency to libdex, without
> propagating it to sysprof.
> 
> Fixes: a73ef093f7b40297d69c6813c44fd4626883632e ("package/libdex: needs 
> ucontext")
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-09-15 17:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 21:39 [Buildroot] [PATCH] package/sysprof: propagate ucontext-related dependency from libdex Thomas Petazzoni via buildroot
2026-09-15 17:22 ` Julien Olivain via buildroot [this message]
2026-09-25 14:44 ` Raphaël Mélotte via buildroot

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=58bcdc3c74bd0df31763ec3708cd01ae@free.fr \
    --to=buildroot@buildroot.org \
    --cc=aperez@igalia.com \
    --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.