From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] norm: fix build failure with old headers
Date: Thu, 31 Mar 2016 13:23:01 -0300 [thread overview]
Message-ID: <56FD4EE5.9000701@zacarias.com.ar> (raw)
In-Reply-To: <20160331181848.00984a4f@free-electrons.com>
On 31/03/16 13:18, Thomas Petazzoni wrote:
> Applied to master, thanks. It would be good to submit the patch
> upstream. Maybe the patch is not acceptable as-is because it will break
> with older versions of libnetfilter_queue, but I guess an autoconf
> check can be added for that.
Hi.
Indeed it's probably not acceptable for old netfilter_queue
compatibility, though i made it the quick way since it was polluting the
autobuilders.
It's waf, my famous friend, i'll try to cook up a failproof test for it,
unfortunately netfilter_queue doesn't version the API in a visible way,
so maybe a pkg-config though i need to consult the author/maintainer
since it would be a new dependency to build.
Regards.
next prev parent reply other threads:[~2016-03-31 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 13:45 [Buildroot] [PATCH] norm: fix build failure with old headers Gustavo Zacarias
2016-03-31 16:18 ` Thomas Petazzoni
2016-03-31 16:23 ` Gustavo Zacarias [this message]
2016-03-31 16:30 ` Thomas Petazzoni
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=56FD4EE5.9000701@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.