ISP uses 1.4, I use 1.5.1 with extensions - What to do?
Kevin Ehmka
running python 1.4? I using 1.5.1 on NT and Linux Redhat 5.1 with swig
generated files. There's nothing in my python code or extention that should
prevent it from being 1.4 compatible.
I don't have access to any libs or includes (like Python.h), can't install
an RPM, haven't found Python1.4 at python.org and, without root privileges
(and being a Linux newbie, my background is C++/Windows), I'm finding it
difficult to completely build the 1.5.1 source.
The options I see are:
Dump my ISP for one running 1.5 (I'm currently using CIHOST). Quite severe.
Does anyone know an ISP who is?
Build the 1.5 source and install it in my personal bin. Is this possible
without system privileges?
Build the 1.4 source or get ready made binaries and includes for Linux 4.x.
Any help would be appreciated from this python newbie.
Kevin
P.S. Since this is my first post, I want to thank Guido and the rest of the
Python community for making available such a cool, kick-ass language.
Oleg Broytmann
On Mon, 14 Dec 1998, Kevin Ehmka wrote:
> The options I see are:
>
> Dump my ISP for one running 1.5 (I'm currently using CIHOST). Quite severe.
> Does anyone know an ISP who is?
There are many - search comp.lang.python for "python-friendly ISP"
> Build the 1.5 source and install it in my personal bin. Is this possible
> without system privileges?
Easily. The only thing you need - to run ./configure --prefix=/path/to/my/dir
After this, make and make install. Install will create bin and lib
subdirectories in /path/to/my/dir, so you need to run
/path/to/my/dir/bin/python myscript.py.
Oleg.
----
Oleg Broytmann National Research Surgery Centre http://sun.med.ru/~phd/
Programmers don't die, they just GOSUB without RETURN.
Kevin Ehmka
On Tue, 15 Dec 1998, Oleg Broytmann wrote:
> Easily. The only thing you need - to run ./configure --prefix=/path/to/my/dir
> After this, make and make install. Install will create bin and lib
> subdirectories in /path/to/my/dir, so you need to run
> /path/to/my/dir/bin/python myscript.py.
>
Oleg,
./configure fails to run with the ac_default_prefix set to /usr/local.
When I remove it or replace it with my own path, all goes well when I use
the prefix option to ./configure as you specified above.
When I attempt to make I get this message:
', needed by `Makefile'. Stop.t `config.status
I don't know what this is all about. I looked at the config.log and that
shows the usual printout. I've also deleted the generated files to make
sure I have a clean configure.
Any help is appreciated.
Kevin
Oleg Broytmann
On Tue, 15 Dec 1998, Kevin Ehmka wrote:
> > Easily. The only thing you need - to run ./configure --prefix=/path/to/my/dir
>
> ./configure fails to run with the ac_default_prefix set to /usr/local.
Here is exactly command line I used a minute ago:
OPT=-O2 CC=gcc LDFLAGS=-s ./configure --prefix=/opt/python
I haven't experienced any problem.
What platform are you using, what compiler? What Python version you
aretrying to compile? Did you apply all patches?
Jimmie Houchin
wrote:
>How can I get my python extension library built on my ISP's Linux platform
>running python 1.4? I using 1.5.1 on NT and Linux Redhat 5.1 with swig
>generated files. There's nothing in my python code or extention that should
>prevent it from being 1.4 compatible.
>
>I don't have access to any libs or includes (like Python.h), can't install
>an RPM, haven't found Python1.4 at python.org and, without root privileges
>(and being a Linux newbie, my background is C++/Windows), I'm finding it
>difficult to completely build the 1.5.1 source.
>
>The options I see are:
>
>Dump my ISP for one running 1.5 (I'm currently using CIHOST). Quite severe.
>Does anyone know an ISP who is
>
>Build the 1.5 source and install it in my personal bin. Is this possible
>without system privileges?
Hello,
I went thru this myself a few weeks ago. I also use CIHOST
(currently). They denied my request to add 1.5.x service.
I am not a C/C++ Programmer, nor a Linux user, but with a few words of
advice I was able to successful compile Python 1.5.1 to my personal
directory.
One of the words of advice was to not install it to the cgi-bin
directory. I didn't know it would run outside of the cgi-bin, but all
works well.
I simply uploaded the tar.gz file untarred it and compiled it
according to the directions in the source. The only thing I did
outside of the defaults was to tell it the directory to install to.
I actually compiled it three times. Each time successful without
problems. I got a different piece of advice after my first two
installs. The third one got to stay. :)
Jimmie Houchin