From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Fu, Qiaobin" <qiaobinf@bu.edu>, "dev@dpdk.org" <dev@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] Patch compilation failure
Date: Mon, 23 Jul 2018 09:24:32 +0100 [thread overview]
Message-ID: <12fa2bcc-568b-933b-335d-ec775fbbbde3@intel.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8977F8FEF44@IRSMSX107.ger.corp.intel.com>
On 23-Jul-18 8:57 AM, De Lara Guarch, Pablo wrote:
> Hi Qiaobin,
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Fu, Qiaobin
>> Sent: Saturday, July 21, 2018 7:58 PM
>> To: dev@dpdk.org
>> Cc: Fu, Qiaobin <qiaobinf@bu.edu>
>> Subject: [dpdk-dev] Patch compilation failure
>>
>> Dear DPDK developers,
>>
>> When I submitted a DPDK patch (http://patchwork.dpdk.org/patch/43090/),
>> however, there is a compilation issue (http://mails.dpdk.org/archives/test-
>> report/2018-July/060307.html).
>>
>> When I tried to compile it in our local machine using the Target: x86_64-native-
>> linuxapp-gcc-shared, it shows that
>>
>> make[1]: *** No rule to make target ‘~/dpdk/config/defconfig_x86_64-native-
>> linuxapp-gcc-shared’
>>
>> I checked the latest DPDK code, and it indeed doesn’t include the above target
>> rule. I did some research online, however, I didn’t figure this out. Could you
>> please help this?
>
> You should use target "x86_64-native-linuxapp-gcc", enabling
> CONFIG_RTE_BUILD_SHARED_LIB in the config file.
Should this information be something we include in the CI email?
>
> Pablo
>
>>
>> Thanks,
>> Qiaobin
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-07-23 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 18:57 Fu, Qiaobin
2018-07-23 7:57 ` De Lara Guarch, Pablo
2018-07-23 8:24 ` Burakov, Anatoly [this message]
2018-07-28 18:18 ` Fu, Qiaobin
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=12fa2bcc-568b-933b-335d-ec775fbbbde3@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=qiaobinf@bu.edu \
--cc=thomas@monjalon.net \
/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).