All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Iptables incompatible with linux-headers!
Date: Tue, 15 May 2007 12:18:50 +0200	[thread overview]
Message-ID: <20070515101850.GA17144@aon.at> (raw)
In-Reply-To: <1179223088.3613.14.camel@localhost>

On Tue, May 15, 2007 at 11:58:08AM +0200, Mats Erik Andersson wrote:
>I have been able to reproduce the strange phenomenon
>that a buildroot setting of
>
>gcc-3.4.4
>binutils-2.17
>buildroot-20070514
>uClibc-0.9.28.3
>busybox-1.5.0
>linux-headers-2.4.27
>dropbear
>iptables-1.3.7 (and 1.3.5)
>
>cannot compile
>
>    iptables-1.3.7/extensions/libipt_string.c
>
>due to non-existing structure members of ipt_string_info.
>However, when I finally got the idea to alter the value
>inside
>
>      package/iptables/iptables.mk
>
>to explicitely replace the header reference by the directory
>
>       KERNEL_DIR=/tmp2/linux-2.4.27
>
>where I separately compiled the kernel, the previous failure is
>changed into success. 

IIRC iptables needs to pickup some kernel-headers. If you use old
versions of linux (old as in not in buildroot), then you should be able
to pass KERNEL_DIR=/there/ to the toplevel make and all should be well.
I did never try if this works, though, so it's possible that you have to
tweak it a little bit (and send the resulting patch which makes sure
that KERNEL_DIR is properly seen in package/* to the list).
>
>Until today I have only used Buildroot for 2.6-kernels
>and I did never encounter the same failure. Would someone
>venture to call this a bug, or is it my handling that could
>have caused my troubles? Aside from one complaint on getopt.h
>when I aimed at a SuSv3-version, the above was the only trouble
>I had in this setting.

I don't remember any details about this getopt thing, i fear..

      reply	other threads:[~2007-05-15 10:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1179181946.6609.17.camel@localhost>
2007-05-15  9:58 ` [Buildroot] Iptables incompatible with linux-headers! Mats Erik Andersson
2007-05-15 10:18   ` Bernhard Fischer [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=20070515101850.GA17144@aon.at \
    --to=rep.dot.nop@gmail.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 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.