From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problems with i686_defconfig
Date: Wed, 14 Apr 2010 11:33:38 +0100 [thread overview]
Message-ID: <4BC59A02.40804@carallon.com> (raw)
Hello,
Using latest from git I am trying to build i686_defconfig but I am
having problems.
The first annoyance is that the defconfig is so old that you have go
through selecting the defaults for all the new config options.
Presumably we should update the defconfigs so they contain all the
default options already set? If so I'm happy to look at a patch.
If I select all the defaults I end up with kernel headers 2.6.33.2,
uClibc 0.9.31, binutils 2.20.1, gcc 4.4.3 and linux 2.6.33.2
You then get the same problems again with uClibc config and linux
config, both ask about config options, should we be updating our
defaults so this step is not necessary?
Finally the build fails in either gdbserver (if selected) or busybox,
complaining the symbol usleep is undefined. Anyone seen this before? Is
it some config problem with uClibc 0.9.31?
next reply other threads:[~2010-04-14 10:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 10:33 Will Wagner [this message]
2010-04-14 16:38 ` [Buildroot] Problems with i686_defconfig Baruch Siach
2010-04-14 18:55 ` Peter Korsgaard
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=4BC59A02.40804@carallon.com \
--to=will_wagner@carallon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox