From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Montorsi, Francesco" <fmontorsi@empirix.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] "cannot use T= with gcov target" when doing "makefile clean" with DPDK-2.1.0
Date: Wed, 2 Sep 2015 14:32:18 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE202302134@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <dbd2038b45054ab28775f311d2ccbd67@bilemail1.empirix.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Montorsi, Francesco
> Sent: Friday, August 28, 2015 10:07 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] "cannot use T= with gcov target" when doing "makefile
> clean" with DPDK-2.1.0
>
> Hi all,
>
> I found that after unzipping dpdk-2.1.0.tar.gz if I run:
> # make T=x86_64-native-linuxapp-gcc O=x86_64-native-linuxapp-gcc
> config
> And then
> # make V=1 T=x86_64-native-linuxapp-gcc O=x86_64-native-linuxapp-gcc
> clean
>
> I get:
>
> [...]
> == Clean app/proc_info
> make -f /home/fmontorsi/Downloads/dpdk-2.1.0/GNUmakefile gcovclean make -f
> /home/fmontorsi/Downloads/dpdk-2.1.0/mk/rte.sdkgcov.mk gcovclean
> /home/fmontorsi/Downloads/dpdk-2.1.0/mk/rte.sdkgcov.mk:34: *** "Cannot use
> T= with gcov target". Stop.
> make[2]: *** [gcovclean] Error 2
> make[1]: *** [clean] Error 2
> make: *** [clean] Error 2
>
> I guess the fix is:
>
Hi Francesco,
That fix seems reasonable and you should submit it as a patch.
There may be other ways to fix this (there are several ways to fix things within the build system) but if you submit a patch we can get some comments.
John.
--
next prev parent reply other threads:[~2015-09-02 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 9:06 Montorsi, Francesco
2015-09-02 14:32 ` Mcnamara, John [this message]
2015-09-04 8:50 ` Montorsi, Francesco
2015-09-07 7:57 ` Olivier MATZ
2015-09-29 16:06 ` Montorsi, Francesco
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=B27915DBBA3421428155699D51E4CFE202302134@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=fmontorsi@empirix.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).