mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] dropwatch: new package
Date: Tue, 20 Jun 2017 10:54:01 +0200	[thread overview]
Message-ID: <20170620085401.lhodepibb3u7k4bt@pengutronix.de> (raw)
In-Reply-To: <20170620080620.GC28640@falbala.home.lespocky.de>

On Tue, Jun 20, 2017 at 10:06:21AM +0200, Alexander Dahl wrote:
> On Tue, Jun 20, 2017 at 09:39:26AM +0200, Michael Olbrich wrote:
> > On Mon, Jun 19, 2017 at 10:39:22AM +0200, Alexander Dahl wrote:
> > > This adds a new package 'dropwatch', a tool for seeing where packets are
> > > dropped in the kernel. It was recently moved to a new upstream URL and
> > > is currently only available from Git. Included is one patch from
> > > buildroot, which is not yet upstream. Tested on an at91sam9g20 platform.
> > > 
> > 
> > lookup.c:36:17: fatal error: bfd.h: No such file or directory
> > compilation terminated.
> > make[2]: *** [lookup.o] Error 1
> > make[1]: *** [build] Error 2
> 
> Probably. The header comes from binutils. So maybe a simple SELECT
> BINUTILS would do?

Probably.

Michael


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2017-06-20  8:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19  8:39 Alexander Dahl
2017-06-20  7:39 ` Michael Olbrich
2017-06-20  8:06   ` Alexander Dahl
2017-06-20  8:54     ` Michael Olbrich [this message]

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=20170620085401.lhodepibb3u7k4bt@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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