Hi All,
Somehow I missed the removal of the 'xstr(...)' when I generated the
source for 1.0.0. I've committed the appropriate change to svn, and
have built a Windows binary installer for rpy, which I will post once
I've run through the tests to ensure that everything else is happy...
-G
On Nov 29, 2007, at 4:34AM , John Reid wrote:
Hi,
Manuzhai's patch works for me. I ended up using
gcc version 3.4.4 (cygming special, gdc 0.12, using dmd 0.125)
although I don't think that made a difference. I didn't compile R,
I'm just using the 2.6 binary version.
Hope this info is useful,
John.
Brian Miles wrote:
Hello,
Like others, I downloaded and built the 1.0.0 sources and still
have this silent crash on "import rpy". I again applied
Manuzhai's "fix" <http://hg.xavamedia.nl/rpy/rev/dabea0379d84> to
src/rpymodule.c and everything works for me (using R 2.5.1 under
Python 2.5.1 under XP SP2, compiled with mingw/gcc 3.4.5
downloaded from http://www.murdoch-sutherland.com/Rtools/ ).
I've attached a patch that has this workaround for win32. I don't
have a version of R with debugging enabled, so I don't know why
the xstr macro is causing a problem under Windows.
John, have you tried a different version of mingw as you suggested
in your message of 11/22? If so, what results have you seen?
Gregory, have you done a win32 build of 1.0.0? If so, what
version of mingw did you use? Further, could you post a win32
build so that we might try it?
Brian
On Nov 28, 2007, at 9:45 AM, rpy-list-
[EMAIL PROTECTED] wrote:
Date: Wed, 28 Nov 2007 09:44:17 -0500
From: "Boldin, Michael" <[EMAIL PROTECTED]>
Subject: [Rpy] RPy & Windows install and import problems
To: <rpy-list@lists.sourceforge.net>
Message-ID:
<[EMAIL PROTECTED]
edu>
Content-Type: text/plain; charset="us-ascii"
For everyone with RPY Windows install and import problems,
The same issue where RPY won't import or work on Windows
installation
seems to be coming up again and again on this list.
I was able to solve it for my Windows XP installation by not
using the
latest and official RPY Windows binary. I used a RC2 build of
December
2006. It seems all RC3 Windows builds of 2007 have this problem and
fiddling with Python and R versions and path settings won't help.
The problem is now on the RPY BUG LIST as
[ 1835064 ] Crash on import rpy (11-20-2007)
and also [ 1827071 ] import error / restart (11-06-2007)
Below is the good news (thanks Greg). A RC3 solution is coming.
It has
not happened yet (as of Nov 28 2007) in the sense that a RPY RC3
Windows
binary with fix has not yet been posted on sourceforge.net
From: Gregory R. Warnes <[EMAIL PROTECTED]> - 2007-11-19 18:58
Hi Everyone,
I've posted RPy 1.0.0 source packages on the sourceforge
download
page at It resolves (I hope) all of the bugs that have been
biting
people: silent failure to start on Windows, problems on 64 bit
systems, and problems with NumPy/Nummary arrays.
Please grab it and take it for a spin.
-Greg
Note that this posting has the source files, not exe builds. If
you do
not build exe's I suggest that you use a RC2 Windows exe build at
this
time.
See
http://sourceforge.net/project/showfiles.php?
group_id=48422&package_id=4
1514
and look under rpy1.0-RC2 (2006-12-11) for
rpy-1.0-RC2.win32-R2.0.0-R-2.4.1-py2.4.exe
or something similarly named (depending on your R and Python
versions).
RPY RC2 and R 2.2 and Python 2.4 worked for me.
I hope this helps someone.
<mime-attachment.txt><mime-attachment.txt>
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
rpy-list mailing list
rpy-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rpy-list
