From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Some AT91SAM9261-EK Notes
Date: Sat, 24 Jan 2009 07:37:31 +0100 [thread overview]
Message-ID: <87k58li504.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <BAY124-DS71A6FE16D4AA2E6DE33BAD2CF0@phx.gbl> (quickx@hotmail.com's message of "Fri\, 23 Jan 2009 15\:06\:42 -0800")
>>>>> "QuickX" == QuickX <quickx@hotmail.com> writes:
QuickX> I was able to narrow down the problem a bit more. It seems that the
QuickX> "UCLIBC_SUPPORT_AI_ADDRCONFIG" is what causes the Segfaults/Core
QuickX> Dumps, however, this option is only available if UCLIBC_USE_NETLINK is
QuickX> set.
QuickX> Results: 0.9.30 (with 0.9.30 config, minus
QuickX> UCLIBC_SUPPORT_AI_ADDRCONFIG) works fine for dropbear and samba.
Ok, thanks, I'll disable it in the defconfig.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2009-01-24 6:37 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
2009-01-23 23:06 ` QuickX
2009-01-24 6:37 ` Peter Korsgaard [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=87k58li504.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