FS/XFS testing framework
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: "fstests@vger.kernel.org" <fstests@vger.kernel.org>
Subject: Re: Failed to compile due to missing <linux/blkdev.h> header with liburing-2.9?
Date: Sat, 8 Feb 2025 15:08:08 -0700	[thread overview]
Message-ID: <7d5bebb8-00f5-4e5e-9c69-67bef353ec79@kernel.dk> (raw)
In-Reply-To: <dfe7dc98-ed02-4a18-8295-ced25f0b500e@gmx.com>

On 2/8/25 1:40 PM, Qu Wenruo wrote:
> 
> 
> 在 2025/2/8 23:41, Jens Axboe 写道:
>> On 2/7/25 8:43 PM, Qu Wenruo wrote:
>>> Hi,
>>>
>>> Just find out that fsstress no longer compiles on for-next (v2025.02.02)
>>> , patches-in-queue (a494849fb48dc6b276c2a1784d6ff66c731e5572) nor master
>>> branchs (8467552f09e1672a02712653b532a84bd46ea10e)
>>> All fails with the following error:
>>>
>>> ```
>>> Building ltp
>>>      [CC]    fsstress
>>> In file included from /usr/include/liburing.h:17,
>>>                   from fsstress.c:30:
>>> /usr/include/liburing/compat.h:11:10: fatal error: linux/blkdev.h: No
>>> such file or directory
>>>     11 | #include <linux/blkdev.h>
>>>        |          ^~~~~~~~~~~~~~~~
>>> ```
>>>
>>> This seems to be a change in the liburing headers, as v2.8 still
>>> compiles fine.
>>>
>>> Is there something wrong with header change?
>>
>> Are you on arch linux? They messed up their packaging.
>>
> 
> Thanks for confirming, will report back to downstream.

Forgot to link it, but also see:

https://github.com/axboe/liburing/issues/1341

which is the same issue on Arch. They compiled the library against
different heads than the version they are installing with, which
caused the issue. They just need to fix their liburing package.

-- 
Jens Axboe


      reply	other threads:[~2025-02-08 22:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-08  3:43 Failed to compile due to missing <linux/blkdev.h> header with liburing-2.9? Qu Wenruo
2025-02-08 13:11 ` Jens Axboe
2025-02-08 20:40   ` Qu Wenruo
2025-02-08 22:08     ` Jens Axboe [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=7d5bebb8-00f5-4e5e-9c69-67bef353ec79@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fstests@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.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