From: Kevin Traynor <ktraynor@redhat.com>
To: "Yu, PingX" <pingx.yu@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Akhil Goyal <akhil.goyal@nxp.com>,
Ali Alnubani <alialnu@mellanox.com>,
"Walker, Benjamin" <benjamin.walker@intel.com>,
David Christensen <drc@linux.vnet.ibm.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
"Stokes, Ian" <ian.stokes@intel.com>,
Jerin Jacob <jerinj@marvell.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
Ju-Hyoung Lee <juhlee@microsoft.com>,
Luca Boccassi <bluca@debian.org>, Pei Zhang <pezhang@redhat.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>,
Raslan Darawsheh <rasland@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>,
"Peng, Yuan" <yuan.peng@intel.com>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: Re: [dpdk-dev] 18.11.3 (LTS) patches review and test
Date: Fri, 11 Oct 2019 10:39:02 +0100 [thread overview]
Message-ID: <255c4bda-d531-cb72-c6c2-b3af212c22cd@redhat.com> (raw)
In-Reply-To: <FD56CD4A6C7E9841B5CD62946D45F34C01B2D79B@SHSMSX104.ccr.corp.intel.com>
On 08/10/2019 11:22, Yu, PingX wrote:
> Kevin,
> FYI. All build are passed in 18.11.3-RC2 except Win10 no support. No issues are found now.
>
Great, thanks for confirming Ping.
Kevin.
> Regards,
> Yu Ping
>
> -----Original Message-----
> From: Kevin Traynor [mailto:ktraynor@redhat.com]
> Sent: Thursday, October 3, 2019 9:30 PM
> To: Yu, PingX <pingx.yu@intel.com>; stable@dpdk.org; dev@dpdk.org
> Cc: Akhil Goyal <akhil.goyal@nxp.com>; Ali Alnubani <alialnu@mellanox.com>; Walker, Benjamin <benjamin.walker@intel.com>; David Christensen <drc@linux.vnet.ibm.com>; Hemant Agrawal <hemant.agrawal@nxp.com>; Stokes, Ian <ian.stokes@intel.com>; Jerin Jacob <jerinj@marvell.com>; Mcnamara, John <john.mcnamara@intel.com>; Ju-Hyoung Lee <juhlee@microsoft.com>; Luca Boccassi <bluca@debian.org>; Pei Zhang <pezhang@redhat.com>; Xu, Qian Q <qian.q.xu@intel.com>; Raslan Darawsheh <rasland@mellanox.com>; Thomas Monjalon <thomas@monjalon.net>; Peng, Yuan <yuan.peng@intel.com>; Chen, Zhaoyan <zhaoyan.chen@intel.com>
> Subject: Re: 18.11.3 (LTS) patches review and test
>
> On 26/09/2019 08:41, Yu, PingX wrote:
>> Kevin,
>> FYi.
>>> 2. [dpdk-stable 18.11.3] meson build error on ub1604-i86
>> Q1: What are the error logs?
>> Please see below Error info.
>>
>> Q2: Is it a regression for you? i.e. did this test pass with 18.11.2?
>> No, it isn't a regression. We don't test it on 18.11.1 and 18.11.2 before, another the test result is still failed after testing.
>> dpdk-stable V18.11.2 commitID(06c4b12a5968caea61e96f7d6bd29d2726fbe255),test failed.
>> dpdk-stable V18.11.1 commitID(16ece46735c9b70b7033ca7ae095930e9038d9fd),test failed, the same mistake.
>>
>> Error info:
>> ninja: Entering directory `build-gcc-static'
>> [296/1419] Compiling C object 'drivers/a715181@@tmp_rte_common_dpaax@sta/common_dpaax_dpaax_iova_table.c.o'.
>> FAILED:
>> drivers/a715181@@tmp_rte_common_dpaax@sta/common_dpaax_dpaax_iova_tabl
>> e.c.o gcc -Idrivers/a715181@@tmp_rte_common_dpaax@sta -Idrivers
>> -I../drivers -Idrivers/common/dpaax -I../drivers/common/dpaax -I.
>> -I../ -Iconfig -I../config -Ilib/librte_eal/common
>> -I../lib/librte_eal/common -Ilib/librte_eal/common/include
>> -I../lib/librte_eal/common/include
>> -Ilib/librte_eal/common/include/arch/x86
>> -I../lib/librte_eal/common/include/arch/x86
>> -I../lib/librte_eal/linuxapp/eal/include
>> -Ilib/librte_eal/linuxapp/eal/../../../librte_compat
>> -I../lib/librte_eal/linuxapp/eal/../../../librte_compat
>> -Ilib/librte_eal -I../lib/librte_eal
>> -Ilib/librte_kvargs/../librte_eal/common/include
>> -I../lib/librte_kvargs/../librte_eal/common/include
>> -Ilib/librte_kvargs -I../lib/librte_kvargs -Ilib/librte_compat
>> -I../lib/librte_compat -fdiagnostics-color=always -pipe
>> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Werror -O3 -include
>> rte_config.h -Wsign-compare -Wcast-qual -Wno-pointer-to-int-cast -fPIC
>> -march=native -D_GNU_SOURCE -DALLOW_EXPERIMENTAL_API -MD -MQ
>> 'drivers/a715181@@tmp_rte_common_dpaax@sta/common_dpaax_dpaax_iova_tab
>> le.c.o' -MF
>> 'drivers/a715181@@tmp_rte_common_dpaax@sta/common_dpaax_dpaax_iova_tab
>> le.c.o.d' -o
>> 'drivers/a715181@@tmp_rte_common_dpaax@sta/common_dpaax_dpaax_iova_tab
>> le.c.o' -c ../drivers/common/dpaax/dpaax_iova_table.c
>> In file included from ../drivers/common/dpaax/dpaax_iova_table.c:8:0:
>> ../drivers/common/dpaax/dpaax_iova_table.c: In function ‘read_memory_node’:
>> ../drivers/common/dpaax/dpaax_logs.h:18:39: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 5 has type ‘__off64_t {aka long long int}’ [-Werror=format=]
>> rte_log(RTE_LOG_DEBUG, dpaax_logger, "dpaax: %s(): " fmt "\n", \
>> ^
>> ../drivers/common/dpaax/dpaax_iova_table.c:102:2: note: in expansion of macro ‘DPAAX_DEBUG’
>> DPAAX_DEBUG("Size of device-tree mem node: %lu", statbuf.st_size);
>> ^
>> ../drivers/common/dpaax/dpaax_logs.h:18:39: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 5 has type ‘__off64_t {aka long long int}’ [-Werror=format=]
>> rte_log(RTE_LOG_DEBUG, dpaax_logger, "dpaax: %s(): " fmt "\n", \
>> ^
>> ../drivers/common/dpaax/dpaax_iova_table.c:121:3: note: in expansion of macro ‘DPAAX_DEBUG’
>> DPAAX_DEBUG("Invalid memory node values or count. (size=%lu)",
>> ^
>> cc1: all warnings being treated as errors [301/1419] Compiling C object 'lib/76b5a35@@rte_pipeline@sta/librte_pipeline_rte_table_action.c.o'.
>> ninja: build stopped: subcommand failed.
>>
> Thanks Yu Ping, I reproduced and applied the commits to fix this. It should be fixed now in RC2 (see other mail). If you could re-run this test to confirm same for you, that would be great.
>
> Kevin.
>
next prev parent reply other threads:[~2019-10-11 9:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 16:31 Kevin Traynor
2019-09-19 10:22 ` Yu, PingX
2019-09-19 21:33 ` Ju-Hyoung Lee
2019-09-19 22:44 ` Abhishek Marathe
2019-09-23 16:18 ` Kevin Traynor
2019-09-25 16:06 ` Kevin Traynor
2019-09-26 7:41 ` Yu, PingX
2019-10-03 13:30 ` Kevin Traynor
2019-10-08 10:22 ` Yu, PingX
2019-10-11 9:39 ` Kevin Traynor [this message]
2019-10-03 13:20 ` Kevin Traynor
[not found] ` <MWHPR21MB083248DEF72934F9291C128B9E970@MWHPR21MB0832.namprd21.prod.outlook.com>
2019-10-11 16:33 ` Ju-Hyoung Lee
2019-10-11 16:49 ` Luca Boccassi
2019-10-11 21:19 ` Kevin Traynor
2019-10-15 16:21 ` [dpdk-dev] [dpdk-stable] " Kevin Traynor
2019-10-15 17:12 ` Abhishek Marathe
2019-10-15 17:19 ` Kevin Traynor
2019-10-22 10:52 ` Kevin Traynor
2019-10-22 17:44 ` Abhishek Marathe
2019-10-22 18:02 ` Kevin Traynor
2019-10-17 13:54 ` Christian Ehrhardt
2019-10-20 13:16 ` Ali Alnubani
2019-10-21 8:54 ` Kevin Traynor
2019-10-04 2:28 ` [dpdk-dev] " Pei Zhang
2019-10-04 9:37 ` Kevin Traynor
2019-10-07 20:01 ` Thinh Tran
2019-10-07 20:11 ` Ju-Hyoung Lee
2019-10-11 9:34 ` Kevin Traynor
2019-10-10 18:39 ` Stokes, Ian
2019-10-11 9:41 ` Kevin Traynor
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=255c4bda-d531-cb72-c6c2-b3af212c22cd@redhat.com \
--to=ktraynor@redhat.com \
--cc=akhil.goyal@nxp.com \
--cc=alialnu@mellanox.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=hemant.agrawal@nxp.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=juhlee@microsoft.com \
--cc=pezhang@redhat.com \
--cc=pingx.yu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@mellanox.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yuan.peng@intel.com \
--cc=zhaoyan.chen@intel.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;
as well as URLs for NNTP newsgroup(s).