All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Nano runtime error
Date: Sat, 24 Oct 2009 20:31:17 +0200	[thread overview]
Message-ID: <87tyxozlsa.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4AE303B6.4090605@ethertek.ca> (Dan Pattison's message of "Sat\, 24 Oct 2009 06\:40\:06 -0700")

>>>>> "Dan" == Dan Pattison <dan.pattison@ethertek.ca> writes:

 Dan> Hello Peter,

Hi,

Please don't mail me directly - That's what we have the mailing list
for.

 Dan> I asked my question on the mailing list but did not receive a
 Dan> reply.

You are too impatient - This is no commercial support system, you only
sent you mail yesterday.

 Dan> Could you please send me the nano binary file compiled for
 Dan> ATMEL ARM AT91SAMG20. I am having problems making mine work on my ARM
 Dan> hardware.

No I cannot. I don't have a rootfs with nano at hand, and even if I did,
the result would presumably be the same.

 Dan> I would like to know if there is a problem with my development
 Dan> environment, or if it is a nano compiling issue. I keep getting
 Dan> the error nano: can't resolve symbol '__ctype_b' when running nano
 Dan> on our hardware.

Have you tried debugging it? Do your C library have a __ctype_b symbol?
From a quick google search there seem(ed) to be some issues with
__ctype_b and uclibc with locales enabled - Do you have locales enabled?

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2009-10-24 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-23  7:15 [Buildroot] Nano runtime error Dan Pattison
     [not found] ` <4AE303B6.4090605@ethertek.ca>
2009-10-24 18:31   ` Peter Korsgaard [this message]
2009-10-24 18:49     ` Dan Pattison
2009-10-24 19:18       ` Peter Korsgaard
2009-10-25 11:54       ` Will Newton

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=87tyxozlsa.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 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.