DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pawel Wodkowski <pawelx.wodkowski@intel.com>
To: Tetsuya Mukawa <mukawa@igel.co.jp>, "dev@dpdk.org" <dev@dpdk.org>,
	 Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] Cannot compile l2fwd-jobstats example
Date: Wed, 25 Feb 2015 08:38:27 +0100	[thread overview]
Message-ID: <54ED7BF3.6060603@intel.com> (raw)
In-Reply-To: <54ED32EE.9090604@igel.co.jp>

On 2015-02-25 03:26, Tetsuya Mukawa wrote:
> Hi,
>
> I cannot compile l2fwd-jobstats using master branch.
> Here is log
>
> $ T=x86_64-native-linuxapp-gcc make examples
> ================== Build examples for x86_64-native-linuxapp-gcc
> == bond
> == cmdline
> == distributor
> == exception_path
> == helloworld
> == ip_pipeline
> == ip_reassembly
> == ipv4_multicast
> == kni
> == l2fwd
> == l2fwd-jobstats
> make: *** l2fwd-jobstats: No such file or directory.  Stop.
> make[2]: *** [l2fwd-jobstats] Error 2
> make[1]: *** [x86_64-native-linuxapp-gcc_examples] Error 2
> make: *** [examples] Error 2
>
>
> As a result of bisecting, it seems after applying below commit, this
> error can be seen.
>
> commit 2caeb8c0141dcf488f2d68aa8e8c44d1f85ed28b
> Author: Pawel Wodkowski <pawelx.wodkowski@intel.com>
> Date:   Tue Feb 24 17:33:24 2015 +0100
>
>      examples/l2fwd-jobstats: new example
>
>
> Thanks,
> Tetsuya
>

Looking on git log, there are missing two files there:

  examples/l2fwd-jobstats/Makefile
  examples/l2fwd-jobstats/main.c

from patch http://dpdk.org/ml/archives/dev/2015-February/014107.html

-- 
Pawel

       reply	other threads:[~2015-02-25  7:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54ED32EE.9090604@igel.co.jp>
2015-02-25  7:38 ` Pawel Wodkowski [this message]
2015-02-25  9:27   ` Thomas Monjalon

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=54ED7BF3.6060603@intel.com \
    --to=pawelx.wodkowski@intel.com \
    --cc=dev@dpdk.org \
    --cc=mukawa@igel.co.jp \
    --cc=thomas.monjalon@6wind.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).