From: J. Spence <j3mail-busybox@rearden.com>
To: buildroot@busybox.net
Subject: [Buildroot] Other build problems
Date: Thu, 13 Mar 2008 06:44:29 -0700 (PDT) [thread overview]
Message-ID: <533595.393981205415869873.JavaMail.root@zmail.rearden.com> (raw)
There seem to be a few other problems with the current tree when building from scratch:
- target/device/x86/i386/linux26.config is using SLAB instead of SLUB, and SLAB seems to be broken in 2.6.24 (the default now)
- target/device/x86/i386/linux26.config is tickling another 2.6.24 problem involving the usercopy module under arch/x86. I guess no-one has built 2.6.24 for anything older than i686 without also enabling generic x86 support, because that triggers a buiild error where the *_intel versions of the symbols are not defined.
- target/devicve/x86/i386/linux26.config cannot be built automatically because some 2.6.24 config items are missing from that default config.
I'd merge the existing config with i386_defconfig from 2.6.24 and send a patch, but I'm looking at my merge utility right now and I'm not sure exactly what the intended strategy of the default buildroot config is. I think that the config is intended to favor small size over speed and features, but I'd like a second opinion before I start deciding for myself what's a mandatory feature in my patch :)
reply other threads:[~2008-03-13 13:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=533595.393981205415869873.JavaMail.root@zmail.rearden.com \
--to=j3mail-busybox@rearden.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.