Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org, Bernd Kuhls <bernd@kuhls.net>
Subject: Re: [Buildroot] [PATCH] package/libcap: add patch to fix build on ARC, OpenRISC, Microblaze
Date: Sat, 19 Apr 2025 15:29:41 +0200	[thread overview]
Message-ID: <20250419152941.1e8aa7ec@windsurf> (raw)
In-Reply-To: <93d4543023f52ff3bb54b6b9198bb9c2@free.fr>

On Sat, 19 Apr 2025 13:19:29 +0200
Julien Olivain <ju.o@free.fr> wrote:

> I also tested with "test-pkg -a" and it seems the xtensa architecture
> has the same problem. See:
> https://gitlab.com/jolivain/buildroot/-/pipelines/1776425781
> https://gitlab.com/jolivain/buildroot/-/jobs/9770003981
> 
> I believe a followup patch will be needed. Could you have
> a look please?

Thanks for the report! I have reported this upstream, and will wait for
their feedback (they were very responsive on the
ARC/OpenRISC/Microblaze report).

Thomas
-- 
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:[~2025-04-19 13:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18 21:41 [Buildroot] [PATCH] package/libcap: add patch to fix build on ARC, OpenRISC, Microblaze Thomas Petazzoni via buildroot
2025-04-19 11:19 ` Julien Olivain
2025-04-19 13:29   ` 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=20250419152941.1e8aa7ec@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox