Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Bark <martin@barkynet.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-01-19
Date: Tue, 21 Jan 2014 10:35:21 +0000	[thread overview]
Message-ID: <52DE4D69.9070506@barkynet.com> (raw)
In-Reply-To: <CAFOYHZB8-NGmU0kEFW2D0cPmLZEE-WuAsuHrZ9R9Wz0f2xtJZg@mail.gmail.com>


Chris, All,

I think i found the issue with the tcpreplay package.  I created a 
minimal defconfig with just a toolchain and tcpreplay and this builds 
fine.  I noticed in the tcpreplay configure output it shows the line

	tcpdump binary path:        /usr/sbin/tcpdump

but this is not in the logs from the auto builds.  So i removed the 
tcpdump package from my host and now tcpreplay fails to build.

I looked in configure.ac and i see it tests for the tcpdump binary on 
the host and if it's found it sets the #define ENABLE_VERBOSE.  The code 
that fails is this

#ifdef ENABLE_VERBOSE
     ctx->options->verbose = value;
     return 0;
#else
     tcpreplay_seterr(ctx, "verbose mode not supported");
     return -1;
#endif

So i can only assume if ENABLE_VERBOSE is not set then tcpreplay does 
not actually compile.

All i did to fix this is set tcpreplay to be dependent on tcpdump and 
point the configure script to look for tcpdump on the target.

I'll post a patch

Thanks


On 20/01/14 23:35, Chris Packham wrote:
> On Tue, Jan 21, 2014 at 10:03 AM, Chris Packham <judge.packham@gmail.com> wrote:
>> On Tue, Jan 21, 2014 at 8:25 AM, Bernd Kuhls <berndkuhls@hotmail.com> wrote:
>>> Chris Packham <judge.packham@gmail.com>
>>> wrote in news:52DCDFDD.3000303 at gmail.com:
>>>
>>>> So far I've not been able to reproduce the issue.
>>>
>>> Hi,
>>>
>>> did you use defconfig[1] used by autobuild like this?
>>> http://permalink.gmane.org/gmane.comp.lib.uclibc.buildroot/68428
>>
>> Not quite my method. I'm actually using the config not defconfig. My
>> steps are this:
>>
>> git clean -fxd
>> git fetch
>> git checkout `curl
>> http://autobuild.buildroot.net/results/c59/c59b8f9d93d77c8b75c02172ff6e6072e8f62228/gitid`
>> curl http://autobuild.buildroot.net/results/c59/c59b8f9d93d77c8b75c02172ff6e6072e8f62228/config
>> | sed 's|/home/test|/home/chrisp|' >.config
>> make
>>
>> I'll try the method mentioned in the link you provided.
>>
>>> I could reproduce the build error with tcpreplay 4.0.2, no known solution
>>> though.
>>>
>>> Regards, Bernd
>>>
>>> [1]
>>> http://autobuild.buildroot.net/results/9d9/9d93582362773bad2dbb495a7796682f43
>>> 2e8915/defconfig
>
> Even with this I can't see a failure. I'm starting to wonder if it has
> some other host tool dependencies.
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>

  reply	other threads:[~2014-01-21 10:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-01-19 Thomas Petazzoni
2014-01-20  8:17 ` Baruch Siach
2014-01-20  8:35 ` Chris Packham
2014-01-20 19:25   ` Bernd Kuhls
2014-01-20 21:03     ` Chris Packham
2014-01-20 23:35       ` Chris Packham
2014-01-21 10:35         ` Martin Bark [this message]
2014-01-22  2:59           ` Chris Packham

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=52DE4D69.9070506@barkynet.com \
    --to=martin@barkynet.com \
    --cc=buildroot@busybox.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