[Buildroot] Python: can't resolve symbol

[Buildroot] Python: can't resolve symbol

[bruce bushby]

Hi

I'm not sure if this is the right list to post this issue to?

From what I can tell, these "can't resolve" messages are caused when
selecting "readline"


# python
Python 2.7.1 (r271:86832, Mar  7 2011, 22:37:34)
[GCC 4.5.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.

python: symbol 'BC': can't resolve symbol

python: symbol 'PC': can't resolve symbol

python: symbol 'UP': can't resolve symbol

python: symbol 'tgetnum': can't resolve symbol

python: symbol 'tgoto': can't resolve symbol

python: symbol 'tgetflag': can't resolve symbol

python: symbol 'tputs': can't resolve symbol

python: symbol 'tgetent': can't resolve symbol

python: symbol 'tgetstr': can't resolve symbol
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110308/ce09482c/attachment-0001.html>

[Buildroot] Python: can't resolve symbol

[Thomas Petazzoni]

Hello,

On Tue, 8 Mar 2011 08:20:39 +0000
bruce bushby <bruce.bushby@gmail.com> wrote:

> >From what I can tell, these "can't resolve" messages are caused when
> selecting "readline"
> 
> 
> # python
> Python 2.7.1 (r271:86832, Mar  7 2011, 22:37:34)
> [GCC 4.5.2] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> python: symbol 'BC': can't resolve symbol
> python: symbol 'PC': can't resolve symbol
> python: symbol 'UP': can't resolve symbol
> python: symbol 'tgetnum': can't resolve symbol
> python: symbol 'tgoto': can't resolve symbol
> python: symbol 'tgetflag': can't resolve symbol
> python: symbol 'tputs': can't resolve symbol
> python: symbol 'tgetent': can't resolve symbol
> python: symbol 'tgetstr': can't resolve symbol
> >>>

It works just fine here, so I presume there is some information leaking
from your host. Could you post somewhere (not on the list, as it
would be too big) :

 * Your Buildroot .config
 * The complete Buildroot build log
 * The build/python-2.7.1/config.log file in your output directory.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Python: can't resolve symbol

[Thomas Petazzoni]

Hello,

Please reply to the list and not to me directly.

On Tue, 8 Mar 2011 09:38:28 +0000
bruce bushby <bruce.bushby@gmail.com> wrote:

> I have seen one of my builds that doesn't have this issue....then I
> changed something which started the issue.....and then I backed out
> the change and the issue went away.....so I'm relatively shore I can
> reproduce it....which if I remember correctly was caused by "readline"
> 
> I'll get two comparative builds together and forward the urls to the
> requested files.

Ok, thanks. Without a way of reproducing the problem, it's hard to
debug it and provide a fix for it.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Python: can't resolve symbol

[bruce bushby]

"..Reply to the list..."  Oops will make sure I reply all.


I think I've managed to replicate my issue, I've tested
two comparative builds which have a single difference:
(env)[veritrack at vdev01 images]$ diff buildroot-with-python-readline.config
buildroot-without-python-readline.config
4c4
< # Tue Mar  8 14:26:17 2011
---
> # Tue Mar  8 14:22:43 2011
445c445
< BR2_PACKAGE_PYTHON_READLINE=y
---
> # BR2_PACKAGE_PYTHON_READLINE is not set
568c568
< BR2_PACKAGE_READLINE=y
---
> # BR2_PACKAGE_READLINE is not set
(env)[veritrack at vdev01 images]$


I ran the build on both (Fedora 12) and (Ubuntu natty 11.04) and the results
are the same, when I select the Python "readline" module I get symbol errors
when launching a python shell. The symbol errors don't appear to cause any
issues ....yet.

I've up laoded my config files and make logs if anybody else wants to try
and replicate the issue:
http://veritrack.co.uk/static/images/buildroot_without_python_readline.config.txt
http://veritrack.co.uk/static/images/buildroot_without_python_readline.makelog.txt
http://veritrack.co.uk/static/images/buildroot_without_python_readline.rootfs.tar.bz2
http://veritrack.co.uk/static/images/buildroot_with_python_readline.config.txt
http://veritrack.co.uk/static/images/buildroot_with_python_readline.makelog.txt
http://veritrack.co.uk/static/images/buildroot_with_python_readline.rootfs.tar.bz2


If you're using "make menuconfig" ...it's:  <packages....> <Interpreter....>
<Python modules><readline>


Thanks
Bruce













On Tue, Mar 8, 2011 at 10:08 AM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Hello,
>
> Please reply to the list and not to me directly.
>
> On Tue, 8 Mar 2011 09:38:28 +0000
> bruce bushby <bruce.bushby@gmail.com> wrote:
>
> > I have seen one of my builds that doesn't have this issue....then I
> > changed something which started the issue.....and then I backed out
> > the change and the issue went away.....so I'm relatively shore I can
> > reproduce it....which if I remember correctly was caused by "readline"
> >
> > I'll get two comparative builds together and forward the urls to the
> > requested files.
>
> Ok, thanks. Without a way of reproducing the problem, it's hard to
> debug it and provide a fix for it.
>
> Regards,
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110308/68408077/attachment.html>

[Buildroot] Python: can't resolve symbol

[bruce bushby]

Hi

I've been having a problem compiling python "readline" module. If I include
the readline python module in my config, I get symbol errors when I start a
python interactive shell.

As a test, I stripped all python and readline from my build "host"
machine....but buildroot complains that it's can't find python. I'm guessing
this is due to the "host-python" directive?

Since my build machine is 32bit Intel and my embedded board/target is
ARM.....why would I need a local install of python to download and compile
python for ARM?

I'm suspecting that python is compiling against my "host's" readline library
and not the readline that should have been compiled for my ARM
target...which I think is what is causing the symbol errors.

So far I've tried the "latest stable" release and the "daily snapshot" on:
Fedora 12 (64bit)
Fedora 14 (32bit)  <-- my current build host
Ubuntu Natty


Bruce







On Tue, Mar 8, 2011 at 8:20 AM, bruce bushby <bruce.bushby@gmail.com> wrote:

> Hi
>
> I'm not sure if this is the right list to post this issue to?
>
> From what I can tell, these "can't resolve" messages are caused when
> selecting "readline"
>
>
> # python
> Python 2.7.1 (r271:86832, Mar  7 2011, 22:37:34)
> [GCC 4.5.2] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>
> python: symbol 'BC': can't resolve symbol
>
> python: symbol 'PC': can't resolve symbol
>
> python: symbol 'UP': can't resolve symbol
>
> python: symbol 'tgetnum': can't resolve symbol
>
> python: symbol 'tgoto': can't resolve symbol
>
> python: symbol 'tgetflag': can't resolve symbol
>
> python: symbol 'tputs': can't resolve symbol
>
> python: symbol 'tgetent': can't resolve symbol
>
> python: symbol 'tgetstr': can't resolve symbol
> >>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110321/6389907a/attachment.html>

[Buildroot] Python: can't resolve symbol

[bruce bushby]

Quick update:

I re-installed Python on my "buildhost"...and then I did a "rpm -e --nodeps"
of the readline and readline-devel rpms, then in build root I did a "make
clean ; make"

That confirmed that buildroot is not "compile python readline" with the
hosts readline includes etc"...but I still get symbol errors.

So digging about a bit further I looked at the readline library on the
embedded OS:
[root at vx-200 ~]# ldd /usr/lib/libreadline.so.6.1
checking sub-depends for '/lib/libc.so.0'
        ld-uClibc.so.0 => /lib//ld-uClibc.so.0 (0x400cc000)
        libc.so.0 => /lib/libc.so.0 (0x00000000)
        /lib//ld-uClibc.so.0 => /lib//ld-uClibc.so.0 (0x00000000)
[root at vx-200 ~]#

I see it it uses both uclibc and libc.  That last line looks looks a bit
dodgy?

So I think I need to look into the readline package/compile....suspect it is
the reason for the symbol errors. Also, I can't "import readline" so the
symbol errors are more
then just informative.

Bruce



Session log starting a python interactive shell and importing readline:

[root at vx-200 ~]# python
Python 2.7.1 (r271:86832, Mar 21 2011, 18:11:40)
[GCC 4.5.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.

python: symbol 'BC': can't resolve symbol

python: symbol 'PC': can't resolve symbol

python: symbol 'UP': can't resolve symbol

python: symbol 'tgetnum': can't resolve symbol

python: symbol 'tgoto': can't resolve symbol

python: symbol 'tgetflag': can't resolve symbol

python: symbol 'tputs': can't resolve symbol

python: symbol 'tgetent': can't resolve symbol

python: symbol 'tgetstr': can't resolve symbol
>>>
>>> import readline

python: symbol 'BC': can't resolve symbol

python: symbol 'PC': can't resolve symbol

python: symbol 'UP': can't resolve symbol

python: symbol 'tgetnum': can't resolve symbol

python: symbol 'tgoto': can't resolve symbol

python: symbol 'tgetflag': can't resolve symbol

python: symbol 'tputs': can't resolve symbol

python: symbol 'tgetent': can't resolve symbol

python: symbol 'tgetstr': can't resolve symbol
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: unknown dlopen() error
>>>






On Mon, Mar 21, 2011 at 4:32 PM, bruce bushby <bruce.bushby@gmail.com>wrote:

>
> Hi
>
> I've been having a problem compiling python "readline" module. If I include
> the readline python module in my config, I get symbol errors when I start a
> python interactive shell.
>
> As a test, I stripped all python and readline from my build "host"
> machine....but buildroot complains that it's can't find python. I'm guessing
> this is due to the "host-python" directive?
>
> Since my build machine is 32bit Intel and my embedded board/target is
> ARM.....why would I need a local install of python to download and compile
> python for ARM?
>
> I'm suspecting that python is compiling against my "host's" readline
> library and not the readline that should have been compiled for my ARM
> target...which I think is what is causing the symbol errors.
>
> So far I've tried the "latest stable" release and the "daily snapshot" on:
> Fedora 12 (64bit)
> Fedora 14 (32bit)  <-- my current build host
> Ubuntu Natty
>
>
> Bruce
>
>
>
>
>
>
>
> On Tue, Mar 8, 2011 at 8:20 AM, bruce bushby <bruce.bushby@gmail.com>wrote:
>
>> Hi
>>
>> I'm not sure if this is the right list to post this issue to?
>>
>> From what I can tell, these "can't resolve" messages are caused when
>> selecting "readline"
>>
>>
>> # python
>> Python 2.7.1 (r271:86832, Mar  7 2011, 22:37:34)
>> [GCC 4.5.2] on linux2
>> Type "help", "copyright", "credits" or "license" for more information.
>>
>> python: symbol 'BC': can't resolve symbol
>>
>> python: symbol 'PC': can't resolve symbol
>>
>> python: symbol 'UP': can't resolve symbol
>>
>> python: symbol 'tgetnum': can't resolve symbol
>>
>> python: symbol 'tgoto': can't resolve symbol
>>
>> python: symbol 'tgetflag': can't resolve symbol
>>
>> python: symbol 'tputs': can't resolve symbol
>>
>> python: symbol 'tgetent': can't resolve symbol
>>
>> python: symbol 'tgetstr': can't resolve symbol
>> >>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110321/68f05a25/attachment.html>

[Buildroot] Python: can't resolve symbol

[bruce bushby]

Hi

UPDATE: Python "readline" issue:

I've determined the errors are related to "ncurses" &
"readline".....readline will compile against ncurses when it finds them. The
definitions at the top of this man page are exactly the ones I'm having a
problem with:
http://linux.die.net/man/3/tgetflag



I've confirmed that when I compile "readline" it locates "ncurses"

I then checked on my embedded system and "libreadline.so" is present AND it
contains the missing symbols:
[root at vx-200 ~]# find / -name "*libreadline*"
/usr/lib/libreadline.so.6.1
/usr/lib/libreadline.so
/usr/lib/libreadline.so.6
[root at vx-200 ~]# strings /usr/lib/libreadline.so.6.1 | grep "tgetflag"
tgetflag
[root at vx-200 ~]# strings /usr/lib/libreadline.so.6.1 | grep "tgetent"
tgetent
[root at vx-200 ~]#


However, the resulting "readline" python module does NOT contain the
symbols:
/usr/lib/python2.7/lib-dynload/readline.so
[root at vx-200 ~]# strings /usr/lib/python2.7/lib-dynload/readline.so | grep
"tgetent"
[root at vx-200 ~]#

My linux desktop also DOES NOT contain the symbols  (However python readline
works on my linux desktop)
[bruce at core ~]$ strings /usr/lib64/python2.6/lib-dynload/readline.so | grep
tgetent
[bruce at core ~]$




I then ran an strace to compare between my pc (Fedora 12) and my embedded OS
that has the python readline issues. The results are similar
and I can see that Python opens the "libncurses" and "libreadline"
libraries....which have been shown to contain the symbols.....however the
embedded
OS still throws errors and can't "import readline"


Linux PC
[bruce at core ~]$ cat X | grep -v "No such file"
open("/usr/lib64/python2.6/lib-dynload/readline.so", O_RDONLY) = 3
open("/usr/lib64/python2.6/lib-dynload/readline.so", O_RDONLY) = 4
open("/etc/ld.so.cache", O_RDONLY)      = 4
open("/lib64/libreadline.so.6", O_RDONLY) = 4
open("/lib64/libtinfo.so.5", O_RDONLY)  = 4
open("/usr/share/terminfo/r/rxvt", O_RDONLY) = 4
open("/etc/inputrc", O_RDONLY)          = 4
open("/usr/lib64/gconv/gconv-modules.cache", O_RDONLY) = 3


Embedded:
[root at vx-200 ~]# cat Y | grep -v "No such file"
open("/usr/lib/python2.7/lib-dynload/readline.so", O_RDONLY|O_LARGEFILE) = 3
open("/usr/lib/python2.7/lib-dynload/readline.so", O_RDONLY) = 4
open("/usr/lib/libreadline.so.6", O_RDONLY) = 4
open("/usr/lib/libncurses.so.5", O_RDONLY) = 4
open("/lib/libc.so.0", O_RDONLY)        = 4
open("/lib/libc.so.0", O_RDONLY)        = 4
open("/lib/libc.so.0", O_RDONLY)        = 4
open("/lib/ld-uClibc.so.0", O_RDONLY)   = 4

python: symbol 'BC': can't resolve symbol

python: symbol 'PC': can't resolve symbol

python: symbol 'UP': can't resolve symbol

python: symbol 'tgetnum': can't resolve symbol

python: symbol 'tgoto': can't resolve symbol

python: symbol 'tgetflag': can't resolve symbol

python: symbol 'tputs': can't resolve symbol

python: symbol 'tgetent': can't resolve symbol

python: symbol 'tgetstr': can't resolve symbol
>>>




>>> import readline

python: symbol 'BC': can't resolve symbol

python: symbol 'PC': can't resolve symbol

python: symbol 'UP': can't resolve symbol

python: symbol 'tgetnum': can't resolve symbol

python: symbol 'tgoto': can't resolve symbol

python: symbol 'tgetflag': can't resolve symbol

python: symbol 'tputs': can't resolve symbol

python: symbol 'tgetent': can't resolve symbol

python: symbol 'tgetstr': can't resolve symbol
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: unknown dlopen() error
>>>


I've been stuck on this since 9th March so any pointers or hints would be
greatly appreciated!!! I'm wondering could it be:
1. That I'm using the buildroot-snapshot?
2. or I'm uClibc-0.9.32-rc2?
3. or that I'm using gcc 4.5.x?
4 or something wrong with Fedora 14?

I'm trying uClibc-0.9.31 now so will know in 40min....but I'm starting to
run out of ideas :(




Bruce




On Tue, Mar 8, 2011 at 8:20 AM, bruce bushby <bruce.bushby@gmail.com> wrote:

> Hi
>
> I'm not sure if this is the right list to post this issue to?
>
> From what I can tell, these "can't resolve" messages are caused when
> selecting "readline"
>
>
> # python
> Python 2.7.1 (r271:86832, Mar  7 2011, 22:37:34)
> [GCC 4.5.2] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>
> python: symbol 'BC': can't resolve symbol
>
> python: symbol 'PC': can't resolve symbol
>
> python: symbol 'UP': can't resolve symbol
>
> python: symbol 'tgetnum': can't resolve symbol
>
> python: symbol 'tgoto': can't resolve symbol
>
> python: symbol 'tgetflag': can't resolve symbol
>
> python: symbol 'tputs': can't resolve symbol
>
> python: symbol 'tgetent': can't resolve symbol
>
> python: symbol 'tgetstr': can't resolve symbol
> >>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110323/1f17b799/attachment-0001.html>

[Buildroot] Python: can't resolve symbol

[bruce bushby]

Could my python "readline" issues have something to do with the uclibc
"dynamic linker" (ld-uClibc.so.0)

When I run python, it opens and reads all the correct files in what appears
to be the correct order:

open("/usr/lib/python2.7/lib-dynload/readline.so", O_RDONLY|O_LARGEFILE) = 3
open("/usr/lib/python2.7/lib-dynload/readline.so", O_RDONLY) = 4
open("/usr/lib/libreadline.so.6", O_RDONLY) = 4
open("/usr/lib/libncurses.so.5", O_RDONLY) = 4
open("/lib/libc.so.0", O_RDONLY)        = 4
open("/lib/libc.so.0", O_RDONLY)        = 4
open("/lib/libc.so.0", O_RDONLY)        = 4
open("/lib/ld-uClibc.so.0", O_RDONLY)   = 4


But immediately after opening "/lib/ld-uClibc.so.0" ... it complains that it
can't resolve  symbols....which is should know about because it's just read
them from /usr/lib/libreadline.so.6. I'm not sure what the "uclibc dynamic
linker" actually does but could it be that it's not linking the libraries
that have just been read?


Bruce




On Wed, Mar 23, 2011 at 1:17 AM, bruce bushby <bruce.bushby@gmail.com>wrote:

> Hi
>
> UPDATE: Python "readline" issue:
>
> I've determined the errors are related to "ncurses" &
> "readline".....readline will compile against ncurses when it finds them. The
> definitions at the top of this man page are exactly the ones I'm having a
> problem with:
> http://linux.die.net/man/3/tgetflag
>
>
>
> I've confirmed that when I compile "readline" it locates "ncurses"
>
> I then checked on my embedded system and "libreadline.so" is present AND it
> contains the missing symbols:
> [root at vx-200 ~]# find / -name "*libreadline*"
> /usr/lib/libreadline.so.6.1
> /usr/lib/libreadline.so
> /usr/lib/libreadline.so.6
> [root at vx-200 ~]# strings /usr/lib/libreadline.so.6.1 | grep "tgetflag"
> tgetflag
> [root at vx-200 ~]# strings /usr/lib/libreadline.so.6.1 | grep "tgetent"
> tgetent
> [root at vx-200 ~]#
>
>
> However, the resulting "readline" python module does NOT contain the
> symbols:
> /usr/lib/python2.7/lib-dynload/readline.so
> [root at vx-200 ~]# strings /usr/lib/python2.7/lib-dynload/readline.so | grep
> "tgetent"
> [root at vx-200 ~]#
>
> My linux desktop also DOES NOT contain the symbols  (However python
> readline works on my linux desktop)
> [bruce at core ~]$ strings /usr/lib64/python2.6/lib-dynload/readline.so |
> grep tgetent
> [bruce at core ~]$
>
>
>
>
> I then ran an strace to compare between my pc (Fedora 12) and my embedded
> OS that has the python readline issues. The results are similar
> and I can see that Python opens the "libncurses" and "libreadline"
> libraries....which have been shown to contain the symbols.....however the
> embedded
> OS still throws errors and can't "import readline"
>
>
> Linux PC
> [bruce at core ~]$ cat X | grep -v "No such file"
> open("/usr/lib64/python2.6/lib-dynload/readline.so", O_RDONLY) = 3
> open("/usr/lib64/python2.6/lib-dynload/readline.so", O_RDONLY) = 4
> open("/etc/ld.so.cache", O_RDONLY)      = 4
> open("/lib64/libreadline.so.6", O_RDONLY) = 4
> open("/lib64/libtinfo.so.5", O_RDONLY)  = 4
> open("/usr/share/terminfo/r/rxvt", O_RDONLY) = 4
> open("/etc/inputrc", O_RDONLY)          = 4
> open("/usr/lib64/gconv/gconv-modules.cache", O_RDONLY) = 3
>
>
> Embedded:
> [root at vx-200 ~]# cat Y | grep -v "No such file"
> open("/usr/lib/python2.7/lib-dynload/readline.so", O_RDONLY|O_LARGEFILE) =
> 3
> open("/usr/lib/python2.7/lib-dynload/readline.so", O_RDONLY) = 4
> open("/usr/lib/libreadline.so.6", O_RDONLY) = 4
> open("/usr/lib/libncurses.so.5", O_RDONLY) = 4
> open("/lib/libc.so.0", O_RDONLY)        = 4
> open("/lib/libc.so.0", O_RDONLY)        = 4
> open("/lib/libc.so.0", O_RDONLY)        = 4
> open("/lib/ld-uClibc.so.0", O_RDONLY)   = 4
>
> python: symbol 'BC': can't resolve symbol
>
> python: symbol 'PC': can't resolve symbol
>
> python: symbol 'UP': can't resolve symbol
>
> python: symbol 'tgetnum': can't resolve symbol
>
> python: symbol 'tgoto': can't resolve symbol
>
> python: symbol 'tgetflag': can't resolve symbol
>
> python: symbol 'tputs': can't resolve symbol
>
> python: symbol 'tgetent': can't resolve symbol
>
> python: symbol 'tgetstr': can't resolve symbol
> >>>
>
>
>
>
> >>> import readline
>
> python: symbol 'BC': can't resolve symbol
>
> python: symbol 'PC': can't resolve symbol
>
> python: symbol 'UP': can't resolve symbol
>
> python: symbol 'tgetnum': can't resolve symbol
>
> python: symbol 'tgoto': can't resolve symbol
>
> python: symbol 'tgetflag': can't resolve symbol
>
> python: symbol 'tputs': can't resolve symbol
>
> python: symbol 'tgetent': can't resolve symbol
>
> python: symbol 'tgetstr': can't resolve symbol
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
> ImportError: unknown dlopen() error
> >>>
>
>
> I've been stuck on this since 9th March so any pointers or hints would be
> greatly appreciated!!! I'm wondering could it be:
> 1. That I'm using the buildroot-snapshot?
> 2. or I'm uClibc-0.9.32-rc2?
> 3. or that I'm using gcc 4.5.x?
> 4 or something wrong with Fedora 14?
>
> I'm trying uClibc-0.9.31 now so will know in 40min....but I'm starting to
> run out of ideas :(
>
>
>
>
> Bruce
>
>
>
>
> On Tue, Mar 8, 2011 at 8:20 AM, bruce bushby <bruce.bushby@gmail.com>wrote:
>
>> Hi
>>
>> I'm not sure if this is the right list to post this issue to?
>>
>> From what I can tell, these "can't resolve" messages are caused when
>> selecting "readline"
>>
>>
>> # python
>> Python 2.7.1 (r271:86832, Mar  7 2011, 22:37:34)
>> [GCC 4.5.2] on linux2
>> Type "help", "copyright", "credits" or "license" for more information.
>>
>> python: symbol 'BC': can't resolve symbol
>>
>> python: symbol 'PC': can't resolve symbol
>>
>> python: symbol 'UP': can't resolve symbol
>>
>> python: symbol 'tgetnum': can't resolve symbol
>>
>> python: symbol 'tgoto': can't resolve symbol
>>
>> python: symbol 'tgetflag': can't resolve symbol
>>
>> python: symbol 'tputs': can't resolve symbol
>>
>> python: symbol 'tgetent': can't resolve symbol
>>
>> python: symbol 'tgetstr': can't resolve symbol
>> >>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110323/67997db0/attachment.html>

[Buildroot] Python: can't resolve symbol

[Mike Frysinger]

On Tue, Mar 8, 2011 at 3:20 AM, bruce bushby wrote:
> # python
> Python 2.7.1 (r271:86832, Mar ?7 2011, 22:37:34)
> [GCC 4.5.2] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> python: symbol 'BC': can't resolve symbol
> python: symbol 'PC': can't resolve symbol
> python: symbol 'UP': can't resolve symbol
> python: symbol 'tgetnum': can't resolve symbol
> python: symbol 'tgoto': can't resolve symbol
> python: symbol 'tgetflag': can't resolve symbol
> python: symbol 'tputs': can't resolve symbol
> python: symbol 'tgetent': can't resolve symbol
> python: symbol 'tgetstr': can't resolve symbol

bug in buildroot.  i'll send a patch.
-mike