From: Leonardo Giordano <lgiordano@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Res: Res: Python / Lua socket programming
Date: Thu, 07 Aug 2008 11:30:46 -0300 [thread overview]
Message-ID: <489B0716.1080102@gmail.com> (raw)
In-Reply-To: <226848.6849.qm@web50403.mail.re2.yahoo.com>
Tiago,
thanks for your reply.
I did the 'export' and it solved some errors/warnings.
However now it says:
#python
'import site' failed; use -v for traceback
Python 2.4.2 (#3, Aug 7 2008, 09:10:04)
[GCC 4.2.4] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>
Then the "import socket" is still failing.
To install python, I just checked it at "make menuconfig" from buildroot.
Regards,
Tiago Maluta escribi?:
> Maybe:
> # export PYTHONHOME=/usr/lib/python2.4.2 or the respective path.
>
> Did you compile this version of Python by hand or get some packed binaries?
>
> --
> Tiago Maluta
>
>
>
> ----- Mensagem original ----
> De: Leonardo Giordano <lgiordano@gmail.com>
> Para: Tiago Maluta <maluta_tiago@yahoo.com.br>
> Cc: buildroot at uclibc.org
> Enviadas: Quinta-feira, 7 de Agosto de 2008 11:15:10
> Assunto: Re: Res: [Buildroot] Python / Lua socket programming
>
> Tiago,
>
> Python is working fine on my host machine. I can do the examples at
> Python Docs.
> However, when tested on my target machine (using linux built with
> buildroot), I see this:
>
> #python
> Could not find platform independent libraries <prefix>
> Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
> 'import site' failed; use -v for traceback
> Python 2.4.2 (#3, Aug 7 2008, 09:10:04)
> [GCC 4.2.4] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>
>
> Then I can import some modules, for instance "import math" and works fine.
> However, when I do "import socket":
>
>
>>>> import socket
>>>>
> Traceback (most recent call last):
> File "<stdin>", line 1, in ?
> ImportError: No module named socket
>
> Any comments?
>
> Regards,
>
>
> Tiago Maluta escribi?:
>
>> Leonardo,
>>
>> Did you followed the Python Docs? http://www.python.org/doc/current/lib/socket-example.html
>> If you are using an operating system based on GNU/Linux, you could check /usr/lib/python2.5 for socket.py
>> Maybe your python installation is missing some modules, try to load other modules (for example: import string, os).
>>
>>
>> -
>> Tiago Maluta
>>
>> ----- Mensagem original ----
>> De: Leonardo Giordano <lgiordano@gmail.com>
>> Para: buildroot at uclibc.org
>> Enviadas: Quinta-feira, 7 de Agosto de 2008 9:27:14
>> Assunto: [Buildroot] Python / Lua socket programming
>>
>> Hi, I am trying to have an easy programming (or scripting) language. I
>> have both Lua and Python compiled with buildroot. However, I don't know
>> how to enable socket programming. I mean:
>> For python, it should have a socket module but it is not. I do "import
>> socket" but is says it is not present. Maybe is a path problem?
>> For lua, I should add luasocket library but I don't know how.
>>
>> Any comments?
>>
>> Regards,
>>
>>
>
>
> Novos endere?os, o Yahoo! que voc? conhece. Crie um email novo com a sua cara @ymail.com ou @rocketmail.com.
> http://br.new.mail.yahoo.com/addresses
>
prev parent reply other threads:[~2008-08-07 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 14:24 [Buildroot] Res: Res: Python / Lua socket programming Tiago Maluta
2008-08-07 14:30 ` Leonardo Giordano [this message]
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=489B0716.1080102@gmail.com \
--to=lgiordano@gmail.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