From: Petr Vorel <pvorel@suse.cz>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] ltp build broken on Fedora 40?
Date: Thu, 29 Aug 2024 22:50:07 +0200 [thread overview]
Message-ID: <20240829205007.GA29837@pevik> (raw)
In-Reply-To: <51DBF795-A185-4E38-993F-E3CAEC37EC83@oracle.com>
> > On Aug 28, 2024, at 6:48 PM, Petr Vorel <pvorel@suse.cz> wrote:
> > Hi Chuck,
> >> Hi-
> >> I'm finding that ltp 20240524 does not build on Fedora 40 due
> >> to a missing header:
> > I guess you need to backport gcc-14 fix b0ae1ee239 ("rpc_svc_1: Fix incompatible
> > pointer type error") [1] (or build with older gcc).
> >> ltp/testcases/kernel/device-drivers/tbio/tbio_kernel/ltp_tbio.c:46:10: fatal error: linux/genhd.h: No such file or directory
> >> 46 | #include <linux/genhd.h>
> >> | ^~~~~~~~~~~~~~~
> >> compilation terminated.
> Building ltp on commit b0ae1ee239 indeed fixed the problem on Fedora 40.
> I guess the "genhd.h" error misdirected me. Thanks, Petr!
You're welcome (we appreciate when kernel maintainers look into LTP),
feel free to ask if you encounter more problems.
I would say mostly the current master branch is the best LTP, I would fallback
to the latest stable release only when master does not build.
Also, in your case, for NFS testing you need just to compile
testcases/network/nfs{,v4} directories and their dependencies
(testcases/lib/ testcases/network/netstress/).
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-08-29 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 20:00 [LTP] ltp build broken on Fedora 40? Chuck Lever III via ltp
2024-08-28 22:48 ` Petr Vorel
2024-08-29 20:14 ` Chuck Lever III via ltp
2024-08-29 20:50 ` Petr Vorel [this message]
2024-08-29 21:23 ` Chuck Lever III via ltp
2024-08-30 2:10 ` Li Wang
2024-09-03 7:24 ` Petr Vorel
2024-09-03 13:42 ` Chuck Lever III via ltp
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=20240829205007.GA29837@pevik \
--to=pvorel@suse.cz \
--cc=chuck.lever@oracle.com \
--cc=ltp@lists.linux.it \
/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