All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pedro Alvarez <pedro.alvarez@codethink.co.uk>
To: netfilter-devel@vger.kernel.org
Subject: [PATCH] ebtables: Cache a copy of the v3.16 kernel headers in the ebtables tree
Date: Thu, 26 Feb 2015 16:37:56 +0000	[thread overview]
Message-ID: <54EF4BE4.4020002@codethink.co.uk> (raw)

Hi everyone.

I've had some problems trying to build ebtables with the v3.19 kernels headers,
failing to build with the following error:

gcc -Wall -Wunused -Werror -fPIC -O3 -DPROGVERSION=\"2.0.10-4\"
-DPROGNAME=\"ebtables\" -DPROGDATE=\"December\ 2011\"
-D_PATH_ETHERTYPES=\"/etc/ethertypes\" -DEBTD_ARGC_MAX=50
-DEBTD_CMDLINE_MAXLN=2048 -DLOCKFILE=\"/var/lib/ebtables/lock\"
-DLOCKDIR=\"/var/lib/ebtables/\" -c -o extensions/ebt_ulog.o
extensions/ebt_ulog.c -Iinclude/
extensions/ebt_ulog.c:17:45: fatal error: linux/netfilter_bridge/ebt_ulog.h: No
such file or directory
 #include <linux/netfilter_bridge/ebt_ulog.h>
                                             ^

After some discussion on IRC we agreed there were 2 possible solutions:

 -1: Disable 'ulog' in the extensions/Makefile

 -2: Cache the headers needed in the ebtables tree.

I decided to go for 2, and here is the patch:

  Repo: git://git.baserock.org/delta/ebtables.git
  Branch: baserock/pedroalvarez/ebt_ulog-fix
  Sha1: 13747a56890cc710b2b4d420edc03a6c2714f40e

NOTE: I didn't want to send a diff, since it would be big and nonsense, but I
can do that if needed.

Regards!

-- 
Pedro

             reply	other threads:[~2015-02-26 16:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 16:37 Pedro Alvarez [this message]
2015-02-26 19:30 ` [PATCH] ebtables: Cache a copy of the v3.16 kernel headers in the ebtables tree Pablo Neira Ayuso
2015-02-26 22:45   ` [PATCHv2] " Pedro Alvarez
2015-02-27 11:23     ` Pablo Neira Ayuso
2015-02-27 11:54     ` [PATCHv3] ebtables: Add kernel headers needed from v3.16 Pedro Alvarez
2015-02-27 11:54       ` [PATCH] " Pedro Alvarez
2015-03-02 11:13         ` Pablo Neira Ayuso

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=54EF4BE4.4020002@codethink.co.uk \
    --to=pedro.alvarez@codethink.co.uk \
    --cc=netfilter-devel@vger.kernel.org \
    /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.