Bug 1562347 - bad compilation on kernel-tests / rpc.h
Summary: bad compilation on kernel-tests / rpc.h
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel-tools
Version: 28
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Laura Abbott
QA Contact: Fedora Extras Quality Assurance
: 1564222 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2018-03-30 09:32 UTC by Cătălin George Feștilă
Modified: 2018-04-05 18:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-04-05 18:02:20 UTC
Type: Bug

Attachments (Terms of Use)

Description Cătălin George Feștilă 2018-03-30 09:32:51 UTC
Description of problem:
using kernel-tests scripts Fedora show me two messages with:
In file included from lib_tcp.c:9:
bench.h:38:10: fatal error: rpc/rpc.h: No such file or directory 
 #include <rpc/rpc.h>
compilation terminated.
gmake[2]: *** [Makefile:224: ../bin/x86_64-linux-gnu/lib_tcp.o] Error 1
make[1] *** [Makefile:114: lmbench] Error 2
mke: *** [Makefile:20: build] Error2

Version-Release number of selected component (if applicable):
Fedora 28 

How reproducible:
Install the kernel-tests tool from git clone https://pagure.io/kernel-tests.git
Run this command on root:
#./runtests.sh -t performance
Steps to Reproduce:
see: https://fedoramagazine.org/running-fedora-kernel-regression-tests/
1. git clone https://pagure.io/kernel-tests.git
2. cd kernel-tests
3. ./runtests.sh -t performance

Actual results:
errors compilation with rpc.h 

Expected results:
upload the test on fedora website

Additional info:

Comment 1 Paul Howarth 2018-03-30 13:48:10 UTC

You'll need to use libtirpc instead.

Comment 2 Jeremy Cline 2018-04-05 17:38:49 UTC
*** Bug 1564222 has been marked as a duplicate of this bug. ***

Comment 3 Jeremy Cline 2018-04-05 18:02:20 UTC
Thanks for the report!

This needs to get fixed in the kernel-tests project so I filed an issue against that project: https://pagure.io/kernel-tests/issue/16

Note You need to log in before you can comment on or make changes to this bug.