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 libpython.so but only a libpython.a .

Now that i think about it i am not sure you can use a stripped library
to link against. how would the linker know the address of those
symbols in this library?

In any case building your own python might be a workaround...

Laurent





2008/11/14 Paul Geeleher <[EMAIL PROTECTED]>:
> 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 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 following
> error when I run "python setup.py install"
>
>
> RHOMES= []
> DEBUG= True
> Setting RHOMES to ['/usr/local/lib64/R']
> ### Using R verion 2.6.2 installed at /usr/local/lib64/R ###
> RHOME= /usr/local/lib64/R
> copying src/rpymodule.c -> src/rpymodule2062.c
> copying src/R_eval.c -> src/R_eval2062.c
> copying src/io.c -> src/io2062.c
> running install
> running build
> running build_py
> running build_ext
> building '_rpy2062' extension
> gcc -pthread -shared build/temp.linux-x86_64-2.5/src/rpymodule2062.o
> build/temp.linux-x86_64-2.5/src/R_eval2062.o
> build/temp.linux-x86_64-2.5/src/io2062.o
> build/temp.linux-x86_64-2.5/src/setenv.o -L/usr/local/lib64/R/bin
> -L/usr/local/lib64/R/lib -L/usr/lib64 -Wl,-R/usr/local/lib64/R/bin
> -Wl,-R/usr/local/lib64/R/lib -lR -lRlapack -lpython2.5 -o
> build/lib.linux-x86_64-2.5/_rpy2062.so
> /usr/lib64/libpython2.5.so: file not recognized: File format not recognized
> collect2: ld returned 1 exit status
> error: command 'gcc' failed with exit status 1
>
> ------------------------------------
>
> So the file libpython2.5.so seems to be throwing up some kind of a problem.
>
> The output of 'file libpython2.5.so' is:
> "libpython2.5.so: symbolic link to `libpython2.5.so.1.0'"
>
> So its a link and the output of 'file libpython2.5.so.1.0' is:
> "libpython2.5.so.1.0: ELF 64-bit LSB shared object, AMD x86-64, version 1
> (SYSV), stripped"
>
>
>
> Any ideas here guys? (please!)
>
> -Paul.
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> rpy-list mailing list
> rpy-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/rpy-list
>
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
rpy-list mailing list
rpy-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rpy-list

Reply via email to