All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot with 2.4.27 kernel: Network problems
Date: Sun, 30 Jan 2011 16:11:58 +0100	[thread overview]
Message-ID: <20110130161158.43d90798@surf> (raw)
In-Reply-To: <20110130145510.5d371b00@x41>

Hello,

On Sun, 30 Jan 2011 14:55:10 +0100
Simon Kagstrom <simon.kagstrom@gmail.com> wrote:

> #
> # Kernel Header Options
> #
> # BR2_KERNEL_HEADERS_2_6_34 is not set
> # BR2_KERNEL_HEADERS_2_6_35 is not set
> BR2_KERNEL_HEADERS_2_6_36=y

If you use the toolchain produced by Buildroot in this configuration to
build your Busybox, then maybe it's this setting causing problem: your
toolchain is built with kernel headers 2.6.36, so its vision of the
userspace <-> kernelspace API/ABI is the one of 2.6.36. And then, you
run your programs with a much, much older kernel.

You should try to build your toolchain with the kernel headers with a
version equal or older to the kernel you're running. Unfortunately,
with a recent Buildroot, you won't be able to specify just "2.4.xx"
version for kernel headers: the mechanism to install kernel headers
when building the toolchain has changed quite a bit between 2.4 and
2.6, and we don't support 2.4 since a long time.

You can probably find some old stuff by looking at the history of
toolchain/kernel-headers/ in Buildroot git, but it's quite likely going
to be a little bit hard to revive the 2.4 support.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2011-01-30 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-30  7:44 [Buildroot] Buildroot with 2.4.27 kernel: Network problems Simon Kagstrom
2011-01-30  9:36 ` Peter Korsgaard
2011-01-30 12:01   ` Simon Kagstrom
2011-01-30 12:43     ` Peter Korsgaard
2011-01-30 13:55       ` Simon Kagstrom
2011-01-30 15:11         ` Thomas Petazzoni [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=20110130161158.43d90798@surf \
    --to=thomas.petazzoni@free-electrons.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.