Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: buildroot@buildroot.org, Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/liburing: Configure liburing with --use-libc
Date: Sat, 30 May 2026 22:27:22 +0200	[thread overview]
Message-ID: <ahtGoRIM5kk-JfTi@windsurf> (raw)
In-Reply-To: <20250331-fix_liburing_arch-v1-1-296318973123@rivosinc.com>

Hello Charlie,

On Mon, Mar 31, 2025 at 06:13:16PM -0700, Charlie Jenkins wrote:
> liburing requires libc when building for any architecture that doesn't
> have built-in syscall support (that is currently any architecture other
> than x86 and aarch64). Configure liburing with --use-libc to allow these
> other architectures to compile.
> 
> Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
> Fixes: 70e3b5a800f8 ("package/liburing: bump to version 2.5")

Sorry for the super long delay in getting back to you. However, it
seems like the issue doesn't exist anymore. First the nolibc mode
exists for RISC-V 64-bit now, and enabling libc seems to be done
automatically on other architectures. I can happily build liburing on
say PowerPC 64 for example. Also our autobuilders are not reporting
any issues.

Building on RISC-V 64-bit, which has nolibc support shows:

nolibc                             yes

during the configure step.

Building for PowerPC 64 build:

nolibc                             no

So I believe your patch is no longer needed.

Best regards,

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:[~2026-05-30 20:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01  1:13 [Buildroot] [PATCH] package/liburing: Configure liburing with --use-libc Charlie Jenkins
2026-05-30 20:27 ` 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=ahtGoRIM5kk-JfTi@windsurf \
    --to=buildroot@buildroot.org \
    --cc=charlie@rivosinc.com \
    --cc=fontaine.fabrice@gmail.com \
    --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