John Owens <john_owens <at> yahoo.com> writes: > > Gregory Warnes <gregory.warnes <at> mac.com> writes:
> > Before trying to modify the default compiler options, try running the > > compler commands that setup.py displays as it tries to work. It > > should pick up the created .o files and proceed to the next step when > > run again. > > I tried that (trace below), had some issues with RPY_SHNAME being > undefined. Perhaps you can offer your expert opinion? Thanks for the > reply! RPY_SHNAME turned out to be a quoting problem, but eventually ... > > If the gcc's are incompatible, then you may have yet another > > problem: python itself will have been built with one, and R the other. ... this stumped me. rpy links with both python (built with the system's gcc, 4.0.1) and R (built with gcc 4.0.4), and Gregory is right, they don't play well together. I'm currently corresponding with the R portfile author to work on this. I'm not sure what to do. R won't build with 4.0.1. I guess I could rebuild python with 4.0.4 and that might be the only way to make it work. Other notes I learned along the way: - gcc 4.0.4 does not work with -Wno-long-double or -no-cpp-precomp, but 4.0.1 does. - Don't start a gcc command line with the first option beginning with -b (as in -bundle), because if a -b is the first argument, it's interpreted differently; I added a -v as the first argument to get around this. JDO ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ rpy-list mailing list rpy-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rpy-list
