From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 62AD4A0C47 for ; Tue, 12 Oct 2021 17:22:36 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E46454113A; Tue, 12 Oct 2021 17:22:35 +0200 (CEST) Received: from forward108o.mail.yandex.net (forward108o.mail.yandex.net [37.140.190.206]) by mails.dpdk.org (Postfix) with ESMTP id 0A776410EF for ; Tue, 12 Oct 2021 17:22:34 +0200 (CEST) Received: from postback4p.mail.yandex.net (postback4p.mail.yandex.net [IPv6:2a02:6b8:c03:773:0:640:94f4:d102]) by forward108o.mail.yandex.net (Yandex) with ESMTP id 5FCB15DD018E for ; Tue, 12 Oct 2021 18:22:34 +0300 (MSK) Received: from forward500j.mail.yandex.net (forward500j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::110]) by postback4p.mail.yandex.net (Yandex) with ESMTP id 5797D5D8FBFE for ; Tue, 12 Oct 2021 18:22:34 +0300 (MSK) Received: from myt5-bc23fd5efdaf.qloud-c.yandex.net (myt5-bc23fd5efdaf.qloud-c.yandex.net [IPv6:2a02:6b8:c12:3ca5:0:640:bc23:fd5e]) by forward500j.mail.yandex.net (Yandex) with ESMTP id 523D36CB640B for ; Tue, 12 Oct 2021 18:22:34 +0300 (MSK) Received: from myt5-cceafa914410.qloud-c.yandex.net (2a02:6b8:c12:3b23:0:640:ccea:fa91 [2a02:6b8:c12:3b23:0:640:ccea:fa91]) by myt5-bc23fd5efdaf.qloud-c.yandex.net (mxback/Yandex) with ESMTP id AUW913SijL-MYD0JDIS; Tue, 12 Oct 2021 18:22:34 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1634052154; bh=tGS7jUHS1I/C1e/qklP+WpzV1TO+b9BFoQRUem+Sfv0=; h=In-Reply-To:Date:References:To:From:Subject:Message-ID; b=BgBwsUJhAMuL7P0qmEM448xYwO2EbOAfj8Zc3kZiS9BSmtt4whpss0rjOPg/YK7iC 1DMm5BRzb0JYyXvLDQjSDC1+W8hOIVkXn5afaHePf7dq7DgnaLknBbhCAkX75HD/Fc UFp0Ho8LGuw/hnMVR4hpSQnvIhYQfmWWjbNbtIow= Authentication-Results: myt5-bc23fd5efdaf.qloud-c.yandex.net; dkim=pass header.i=@yandex.ru Received: by myt5-cceafa914410.qloud-c.yandex.net (smtp/Yandex) with ESMTPS id Xw16jof7YX-MXMuM700; Tue, 12 Oct 2021 18:22:33 +0300 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client certificate not present) X-Yandex-Fwd: 2 Subject: Re: Troubles with building of DPDK.RPM and meson From: "Ruslan R. Laishev" To: users@dpdk.org References: <649b9c26-cf38-2dc3-7148-05f8b8887299@yandex.ru> <2941130.Bb6R3ciPLE@thomas> Organization: StarLet Team Message-ID: <2465ee94-c042-506e-99d5-48c74c573ed8@yandex.ru> Date: Tue, 12 Oct 2021 18:22:32 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 SeaMonkey/2.53.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Installed meson i ninja from .RPM ... Unpack DPDK-20.11.SRC.RPM, now I try to make DPDK.RPM (with the original dpdk.spec from the DPDK 20.11 package), I get : [root@sysman rpmbuild]# rpmbuild -ba SPECS/dpdk.spec Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.r8Q2er + 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.GjKyDK + 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' + %set_build_flags /var/tmp/rpm-tmp.GjKyDK: line 33: fg: no job control error: Bad exit status from /var/tmp/rpm-tmp.GjKyDK (%build) What i missing now ?