From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Some AT91SAM9261-EK Notes
Date: Fri, 23 Jan 2009 21:40:36 +0100 [thread overview]
Message-ID: <87ab9hkb7f.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <BAY124-DS41A02756B01D8CBA35C29D2CF0@phx.gbl> (quickx@hotmail.com's message of "Fri\, 23 Jan 2009 11\:38\:55 -0800")
>>>>> "QuickX" == QuickX <quickx@hotmail.com> writes:
Hi,
QuickX> My guess is that it's the "UCLIBC_USE_NETLINK" option since
QuickX> it looks like only networky applications are affected
QuickX> (dropbear, samba, etc). I'm actually catching a plane in 8
QuickX> hours and will be gone for a week, however, I can try to test
QuickX> the options one by one if you can't tell what it is from just
QuickX> the diff.
You're not the only one having problems with uclibc 0.9.30 and
netlink:
http://lists.uclibc.org/pipermail/uclibc/2009-January/041701.html
Maybe we should just disable it in the 0.9.30 defconfig? What is the
impact of doing that?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-01-23 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 21:19 [Buildroot] Some AT91SAM9261-EK Notes Quick X
2009-01-23 14:53 ` Ulf Samuelsson
2009-01-23 19:38 ` QuickX
2009-01-23 20:40 ` Peter Korsgaard [this message]
2009-01-23 23:06 ` QuickX
2009-01-24 6:37 ` 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=87ab9hkb7f.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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