[Buildroot] Nano runtime error

[Buildroot] Nano runtime error

[Dan Pattison]

Hello List,

With a fresh git clone, configured for Atmel Arm AT91SAMG20, EABI. Nano 
compiles without problem, but I get the error below when running on the 
target.

# nano
nano: can't resolve symbol '__ctype_b'
#

Can someone send me a working ARM binary of nano to test?

Thanks,

-- 
Dan Pattison
Ethertek Circuits

[Buildroot] Nano runtime error

[Peter Korsgaard]

>>>>> "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

[Buildroot] Nano runtime error

[Dan Pattison]

Hello Peter and List,

Sorry for my impatience. I realize this is no commercial support system, 
I stand corrected.

Locals is not enabled in uclibc.

Best Regards,

Dan.

Peter Korsgaard wrote:
>>>>>> "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?
>
>   
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com 
> Version: 8.5.423 / Virus Database: 270.14.29/2455 - Release Date: 10/24/09 06:43:00
>
>   

-- 
Dan Pattison
Ethertek Circuits

[Buildroot] Nano runtime error

[Peter Korsgaard]

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

 Dan> Hello Peter and List,
 Dan> Sorry for my impatience. I realize this is no commercial support
 Dan> system, I stand corrected.

 Dan> Locals is not enabled in uclibc.

FYI, I just did a build for i386 (I already had a partial build
available), and here nano works.

-- 
Bye, Peter Korsgaard

[Buildroot] Nano runtime error

[Will Newton]

On Sat, Oct 24, 2009 at 6:49 PM, Dan Pattison <dan.pattison@ethertek.ca> wrote:
> Hello Peter and List,
>
> Sorry for my impatience. I realize this is no commercial support system, I
> stand corrected.
>
> Locals is not enabled in uclibc.

The error "can't resolve symbol '__ctype_b'" occurs when you build a
binary with a toolchain with locales support disabled and try and run
it with uClibc with locales support enabled.

I would try doing a full rebuild of toolchain and filesystem.