Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Python: can't resolve symbol
Date: Tue, 8 Mar 2011 10:31:59 +0100	[thread overview]
Message-ID: <20110308103159.2ca3d89b@surf> (raw)
In-Reply-To: <AANLkTim9AZ2Q8PZ9SOsBDPEL3Yqn7euZ4hmkKzQ1Dxai@mail.gmail.com>

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

  reply	other threads:[~2011-03-08  9:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08  8:20 [Buildroot] Python: can't resolve symbol bruce bushby
2011-03-08  9:31 ` Thomas Petazzoni [this message]
     [not found]   ` <AANLkTi==DMhkvCiKn+ZKdc=8003+qqaWOgQBf77GkgbV@mail.gmail.com>
2011-03-08 10:08     ` Thomas Petazzoni
2011-03-08 18:20       ` bruce bushby
2011-03-21 16:32 ` bruce bushby
2011-03-21 21:51   ` bruce bushby
2011-03-23  1:17 ` bruce bushby
2011-03-23 10:57   ` bruce bushby
2011-03-23 23:39 ` Mike Frysinger

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=20110308103159.2ca3d89b@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --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