Excellent! I've finally managed to get this working.
I deleted the contents of the "/usr/local/lib/python2.5/site-packages/"
directory, this included the offending "_rpy2062.so" file, setup.py seems to
have recreated the files in this directory using the new python which has
done the trick.
If yo
Excellent! I've finally managed to get this working.
I deleted the contents of the "/usr/local/lib/python2.5/site-packages/"
directory, this included the offending "_rpy2062.so" file, setup.py seems to
have recreated the files in this directory using the new python which has
done the trick.
If yo
Cleaning up manually the previous installs in python-libs may also help
L.
On Mon, 2008-11-17 at 08:23 -0500, laurent oget wrote:
> so you have the right python, but somehow your rpy is looking for
> symbols that are not there. i suspect part of your rpy was leftover
> from the initial built aga
so you have the right python, but somehow your rpy is looking for
symbols that are not there. i suspect part of your rpy was leftover
from the initial built against the old python. one thing you can do is
hide your rpy folder, extract the .tar.gz again and do the python
setup.py install from scratc
Hi,
I'm importing into version 2.5.2. Thats the version that I compiled from
source and that now starts by default when I type "python" at the command
prompt.
-Paul.
On Mon, Nov 17, 2008 at 3:53 AM, laurent oget <[EMAIL PROTECTED]> wrote:
> One question i forgot to ask:
> -which python are you
One question i forgot to ask:
-which python are you importing into?
Laurent
2008/11/16 Paul Geeleher <[EMAIL PROTECTED]>:
> Hi again.
>
> I did a "find / -name "*libpython*"" which should find any libpython files
> (I think). It outputted the following.
>
> /usr/lib/libpython2.4.so.1.0
> /usr/lib
Hi again.
I did a "find / -name "*libpython*"" which should find any libpython files
(I think). It outputted the following.
/usr/lib/libpython2.4.so.1.0
/usr/lib64/libpython2.5.so
/usr/lib64/libpython2.5.so.1.0
/usr/lib64/gnome-vfs-2.0/modules/libpythonmethod.so
/usr/lib64/python2.5/config/libpyt
Is the libpython in /usr/lib being picked up instead of the new one at
runtime? can you put this aside and try again?
2008/11/15 Paul Geeleher <[EMAIL PROTECTED]>:
> Hi again,
>
> Building version 2.5.2 of Python from source (overwriting version
> 2.5.1) seems to have solved that problem alright.
Hi again,
Building version 2.5.2 of Python from source (overwriting version
2.5.1) seems to have solved that problem alright. Rpy now seems to install,
but when I go to import it I'm faced witht he following error:
>>> from rpy import *
Traceback (most recent call last):
File "", line 1, in
Thanks for the response Laurent. I'll give it a go and let you know how it
works out.
-Paul.
On Fri, Nov 14, 2008 at 7:18 PM, laurent oget <[EMAIL PROTECTED]> wrote:
> This definitely looks weird. I have built rpy and rpy2 on 64-bit
> linux, but this was always using a python i built before, si
This definitely looks weird. I have built rpy and rpy2 on 64-bit
linux, but this was always using a python i built before, since the
machine i am using come with an antiquated python in the distribution.
I just looked at one of those machine and I noticed my hand-built
python does not have a libpy
Hi
I posted this message about 10 days ago and I didn't get a reply, so I'm
going to chance re-posting, hopefully somebody can help me out because I
still haven't managed to fix it...
___
Hi all,
I'm trying to install Rpy on a 64 bit Suse Enterprise Edition Server. I'm
running R ve
Hi all,
I'm trying to install Rpy on a 64 bit Suse Enterprise Edition Server. I'm
running R version 2.6.2 and python version 2.5.1 and Rpy 1.0.3. I've set up
the path
to the R library by creating a link to libR.so and running ldconfig.
I've got the python-devel package installed. I'm getting the f
13 matches
Mail list logo
