On Tue, 16 Apr 2013 17:22:55 +0300, Anssi Saari wrote:
>In any case, cross compiling Python shouldn't be that hard. I
>just recently built 2.7.3 for my OpenWRT router since the packaged
>Python didn't have readline support (some long standing linking issue
>with readline and ncurses and uClibc).
Gilles writes:
> I see Python mentioned in /usr/lib and /usr/share, and was wondering
> if all it'd take to solve this issue, is just to cross-compile the
> interpreter and the rest is just CPU-agnostic Python scripts.
I suppose. In any case, cross compiling Python shouldn't be that hard. I
just
On 4/15/2013 11:20 AM, Gilles wrote:
Hello
I tried running uWSGI on an ARM-based appliance, but it fails.
Apparently, it could be due to the official Python 2.6.6 interpreter
in the depot not being compiled the way uWSGI expects it to be:
./configure --enable-shared; make; make install;
www.ra
In message <4c911670$0$41115$e4fe5...@news.xs4all.nl>, Hans Mulder wrote:
> The most popular way to get the latter problem is to write the script
> on a Windows box and then upload it to Unix box using FTP in binary
> mode (or some other transport that doesn't adjust the line endings).
I always t
Thomas Jollans wrote:
On Tuesday 14 September 2010, it occurred to Neil Benn to exclaim:
#
./python
-sh: ./python: not found
I'm guessing either there is no file ./python, or /bin/sh is fundamentally
broken.
or ./python is a symlink to a file that does not exist, or ./python
is a scr
On Tuesday 14 September 2010 21:19, Thomas Jollans wrote:
> On Tuesday 14 September 2010, it occurred to Neil Benn to exclaim:
>> #
>> ./python
>>
>> -sh: ./python: not found
>
>
> I'm guessing either there is no file ./python, or /bin/sh is fundamentally
> broken.
Yes, it may be instructive t
On Tuesday 14 September 2010, it occurred to Neil Benn to exclaim:
> #
> ./python
>
> -sh: ./python: not found
I'm guessing either there is no file ./python, or /bin/sh is fundamentally
broken.
--
http://mail.python.org/mailman/listinfo/python-list
