From: Daniele Salvatore Albano <info@daccii.it>
To: buildroot@busybox.net
Subject: [Buildroot] connman fails on uclibc
Date: Sun, 05 Feb 2012 15:07:27 +0100 [thread overview]
Message-ID: <4F2E8D1F.60600@daccii.it> (raw)
I'm trying to get connman working on uclibc.
I've seen that connman has been commited to git so i've pulled last
updates and trying with them.
However, i got two problems:
- connman wants uclibc snapshot, but uclibc-0.9.33 sholdn't works fine?
resolver isn't there?
- connman wants backtrace support that, as far i understand, is a glibc
specific feature, so i've made a simple patch to avoid using backtrace
on uclibc, but there isn't any way to have backtrace on uclibc to make
connman happy?
I'm using ct-ng 1.14.0 patched to support uclibc 0.9.33.
Initially i've compiled the toolchain with only
UCLIBC_HAS_RESOLVER_SUPPORT without any success because connman
configure continued to fail (ns_initparse symbol/resolver missing), so
i've selected UCLIBC_HAS_LIBRESOLV_STUB, but i don't know if it will
work, i'm yet compiling.
Any ideas?
Best Regards,
Daniele
--
____________________________________________________________
|
Daniele Salvatore Albano | web site:
IT Consultant | http://www.itechcon.it
Mobile Software Development | http://www.daccii.it
Webapps Design and Development |
Software Engineer and Developer | e-mail:
Linux Servers SetUp And Administration | info at itechcon.it
Embedded Network Solutions | d.albano at itechcon.it
Are you lazy? Take a look to LazyDroid (www.lazydroid.net): android for
lazy people!
Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute in
questo messaggio sono riservate ed a uso esclusivo del destinatario.
Qualora il messaggio in parola Le fosse pervenuto per errore, La
invitiamo ad eliminarlo senza copiarlo e a non inoltrarlo a terzi,
dandocene gentilmente comunicazione. Grazie.
Pursuant to Legislative Decree No. 196/2003, you are hereby informed
that this message contains confidential information intended only for
the use of the addressee. If you are not the addressee, and have
received this message by mistake, please delete it and immediately
notify us. You may not copy or disseminate this message to anyone. Thank
you.
reply other threads:[~2012-02-05 14:07 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=4F2E8D1F.60600@daccii.it \
--to=info@daccii.it \
--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