All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mats Erik Andersson <mats.andersson64@comhem.se>
To: buildroot@busybox.net
Subject: [Buildroot] Iptables incompatible with linux-headers!
Date: Tue, 15 May 2007 11:58:08 +0200	[thread overview]
Message-ID: <1179223088.3613.14.camel@localhost> (raw)
In-Reply-To: <1179181946.6609.17.camel@localhost>

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. 

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.

Regards,   Mats Erik Andersson

       reply	other threads:[~2007-05-15  9:58 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 ` Mats Erik Andersson [this message]
2007-05-15 10:18   ` [Buildroot] Iptables incompatible with linux-headers! Bernhard Fischer

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=1179223088.3613.14.camel@localhost \
    --to=mats.andersson64@comhem.se \
    --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.