From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Fixed tcpreplay auto build errors
Date: Thu, 23 Jan 2014 08:37:14 +0100 [thread overview]
Message-ID: <87txcvb13p.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAFOYHZDmMG8iMshnUwwdgoNeG2g+Xe3DaVbsfTyyz8WzsOsy9Q@mail.gmail.com> (Chris Packham's message of "Thu, 23 Jan 2014 13:54:10 +1300")
>>>>> "Chris" == Chris Packham <judge.packham@gmail.com> writes:
Hi,
> I'm already working on an upstream fix
> https://github.com/appneta/tcpreplay/pull/60 just waiting to hear some
> feedback. Buildroot could carry my patch or just wait for the change
> to be merged upstream. I've also got a different change needed for
> x86_64 but I think that's more a ubuntu/debian thing than a x86_64
> architecture thing.
> Mine is a slightly different solution to what you suggest. Doing some
> grepping through the tcpreplay source it looks like my solution of
> adding a format string has been used in other places.
Ahh ok, yes - It also works to change the callers of the macro,
naturally. Lets see what upstream says.
> I'll take a look at your suggestion for TCPREPLAY_CONF_ENV and see if
> I can come up with a solution that works when cross compiling.
Thanks!
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-01-23 7:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 10:41 [Buildroot] [PATCH 1/1] Fixed tcpreplay auto build errors Martin Bark
2014-01-22 3:07 ` Chris Packham
2014-01-22 8:58 ` Peter Korsgaard
2014-01-23 0:54 ` Chris Packham
2014-01-23 7:37 ` Peter Korsgaard [this message]
2014-01-23 9:07 ` [Buildroot] [PATCH] tcpreplay: cross-compile with tcpdump support Chris Packham
2014-01-23 11:30 ` Peter Korsgaard
2014-01-23 20:08 ` Martin Bark
2014-01-23 21:31 ` Peter Korsgaard
2014-01-23 22:47 ` Chris Packham
2014-01-27 14:26 ` Peter Korsgaard
2014-01-28 9:37 ` [Buildroot] [PATCH] tcpreplay: Bump version to 4.0.2 Chris Packham
2014-01-28 10:28 ` Peter Korsgaard
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=87txcvb13p.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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