From: "Ruslan R. Laishev" <zator@yandex.ru>
To: users@dpdk.org
Subject: Re: Troubles with building of DPDK.RPM and meson
Date: Tue, 12 Oct 2021 12:10:54 +0300 [thread overview]
Message-ID: <dfa914f9-fdaa-cd4d-5556-81c181f8c3fe@yandex.ru> (raw)
In-Reply-To: <2941130.Bb6R3ciPLE@thomas>
On 12-10-2021 11:31, Thomas Monjalon wrote:
Thanks for the answer.
> 12/10/2021 08:45, Ruslan R. Laishev:
>> Hello All!
>>
>> I have a small study task to make DPDK.RPM with the latest DPDK from
>> the git.
>
> You should look at what is done in Fedora for the latest DPDK.
rpmfind.net return only binary kits for DPDK.
I'm need to make installation kit with building from sources.
>
>> I use DPDK.SPEC from the latest .SRC.RPM kit as a template.
>
> Not sure what is your reference.
Latest .RPM with the source I found is:
dpdk-18.11.8-1.el7_8.src.rpm
Ok. Got DPDK.SPEC from 20.11 from Fedora site , so:
First run:
[root@sysman rpmbuild]# rpmbuild -ba SPECS/dpdk.spec
error: Failed build dependencies:
meson is needed by dpdk-2:20.11-2.el7.x86_64
[root@sysman rpmbuild]#
[root@sysman rpmbuild]# meson -v
0.59.2
[root@sysman rpmbuild]#
If I comment the "BuildRequires: meson" :
[root@sysman rpmbuild]# rpmbuild -ba SPECS/dpdk.spec
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.rMiLfX
+ umask 022
+ cd /root/rpmbuild/BUILD
+ cd /root/rpmbuild/BUILD
+ rm -rf dpdk-20.11
+ /usr/bin/xz -dc /root/rpmbuild/SOURCES/dpdk-20.11.tar.xz
+ /usr/bin/tar -xf -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd dpdk-20.11
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.DIS5o0
+ umask 022
+ cd /root/rpmbuild/BUILD
+ cd dpdk-20.11
++ echo -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches
-m64 -mtune=generic -fcommon
+ CFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches
-m64 -mtune=generic -fcommon'
+ %meson --includedir=include/dpdk -Ddrivers_install_subdir=dpdk-pmds
-Denable_docs=true -Dmachine=default --default-library=shared
/var/tmp/rpm-tmp.DIS5o0: line 32: fg: no job control
error: Bad exit status from /var/tmp/rpm-tmp.DIS5o0 (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.DIS5o0 (%build)
[root@sysman rpmbuild]#
Any ideas ?
next prev parent reply other threads:[~2021-10-12 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 6:45 Ruslan R. Laishev
2021-10-12 8:31 ` Thomas Monjalon
2021-10-12 9:10 ` Ruslan R. Laishev [this message]
2021-10-12 15:22 ` Ruslan R. Laishev
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=dfa914f9-fdaa-cd4d-5556-81c181f8c3fe@yandex.ru \
--to=zator@yandex.ru \
--cc=users@dpdk.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;
as well as URLs for NNTP newsgroup(s).