From: "Milan P. Stanić" <mps@arvanta.net>
To: Jens Axboe <axboe@kernel.dk>
Cc: io-uring@vger.kernel.org
Subject: Re: Building liburing on musl libc gives error that errno.h not found
Date: Mon, 16 Jun 2025 15:06:12 +0200 [thread overview]
Message-ID: <20250616130612.GA21485@m1pro.arvanta.net> (raw)
In-Reply-To: <1198c63d-4fe8-4dda-ae9f-23a9f5dafd5c@kernel.dk>
On Mon, 2025-06-16 at 06:34, Jens Axboe wrote:
> On 6/15/25 1:56 PM, Milan P. Stani? wrote:
> > On Sun, 2025-06-15 at 12:57, Jens Axboe wrote:
> >> On 6/15/25 11:16 AM, Milan P. Stani? wrote:
> >>> Hi,
> >>>
> >>> Trying to build liburing 2.10 on Alpine Linux with musl libc got error
> >>> that errno.h is not found when building examples/zcrx.c
> >>>
> >>> Temporary I disabled build zcrx.c, merge request with patch for Alpine
> >>> is here:
> >>> https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/84981
> >>> I commented in merge request that error.h is glibc specific.
> >>
> >> I killed it, it's not needed and should've been caught during review.
> >> We should probably have alpine/musl as part of the CI...
> >
> > Fine.
> >
> >>> Side note: running `make runtests` gives 'Tests failed (32)'. Not sure
> >>> should I post full log here.
> >>
> >> Either that or file an issue on GH. Sounds like something is very wrong
> >> on the setup if you get failing tests, test suite should generally
> >> pass on the current kernel, or any -stable kernel.
> >>
> > I'm attaching log here to this mail. Actually it is one bug but repeated
> > in different tests, segfaults
>
> Your kernel is ancient, and that will surely account from some of the
> failures you see. A 6.6 stable series from January 2024 is not current
> by any stretch, should definitely upgrade that. But I don't think this
> accounts for all the failures seen, it's more likely there's some musl
> related issue as well which is affecting some of the tests.
This happens also on 6.14.8-1 asahi kernel on apple m1pro machine.
I forgot to mention this in previous mail, sorry.
--
Kind regards
next prev parent reply other threads:[~2025-06-16 13:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-15 17:16 Building liburing on musl libc gives error that errno.h not found Milan P. Stanić
2025-06-15 18:57 ` Jens Axboe
2025-06-15 19:56 ` Milan P. Stanić
2025-06-16 12:34 ` Jens Axboe
2025-06-16 13:06 ` Milan P. Stanić [this message]
2025-06-16 13:59 ` Jens Axboe
2025-06-16 14:18 ` Milan P. Stanić
2025-06-16 15:13 ` Jens Axboe
2025-06-16 15:26 ` Jens Axboe
2025-06-16 15:35 ` Jens Axboe
2025-06-16 16:32 ` Milan P. Stanić
2025-06-16 16:35 ` Jens Axboe
2025-06-16 16:44 ` Milan P. Stanić
2025-06-17 8:19 ` Milan P. Stanić
2025-06-17 11:51 ` Jens Axboe
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=20250616130612.GA21485@m1pro.arvanta.net \
--to=mps@arvanta.net \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
/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