That's better, thanks very much. It is a little strange that the compile messages don't point out missing headers.
Etuka On 3 Sep 2008, at 10:40, [EMAIL PROTECTED] wrote: > > Date: Tue, 02 Sep 2008 21:36:14 -0700 > From: "Nicholas Lewin-Koh" <[EMAIL PROTECTED]> > Subject: Re: [Rpy] RPy Compile Error on OS X 10.5 with Python 2.5.1 R > 2.7.2 > To: "RPy help, support and design discussion list" > <rpy-list@lists.sourceforge.net>, rpy-list@lists.sourceforge.net > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="ISO-8859-1" > > Hi, > Try using the svn version, rpy2-2.0.0a3 is missing headers. > > Nicholas > On Wed, 3 Sep 2008 01:59:07 +0100, "Etuka Onono" <[EMAIL PROTECTED]> > said: >> Hello, >> >> I have the following compile error when trying to build rpy2-2.0.0a3. >>>>> >> building 'rpy2.rinterface.rinterface' extension >> gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused- >> madd -fno-common -dynamic -DNDEBUG -g -Os -Wall -Wstrict-prototypes - >> DMACOSX -I/usr/include/ffi -DENABLE_DTRACE -arch i386 -arch ppc - >> pipe - >> g -DR_INTERFACE_PTRS=1 -DCSTACK_DEFNS=1 -DRIF_HAS_RSIGHAND=1 -I/ >> Library/Frameworks/R.framework/Resources/include -Irpy/rinterface -I/ >> System/Library/Frameworks/Python.framework/Versions/2.5/include/ >> python2.5 -c rpy/rinterface/array.c -o build/temp.macosx-10.5- >> i386-2.5/ >> rpy/rinterface/array.o >> rpy/rinterface/array.c:103: error: syntax error before >> ‘*’ token >> rpy/rinterface/array.c:104: warning: function declaration >> isn’t a >> prototype >> rpy/rinterface/array.c: In function ‘array_struct_get’: >> rpy/rinterface/array.c:105: warning: implicit declaration of function >> ‘RPY_SEXP’ >> rpy/rinterface/array.c:105: error: ‘self’ undeclared >> (first use in >> this function) >> rpy/rinterface/array.c:105: error: (Each undeclared identifier is >> reported only once >> rpy/rinterface/array.c:105: error: for each function it appears in.) >> rpy/rinterface/array.c:105: warning: initialization makes pointer >> from >> integer without a cast >> rpy/rinterface/array.c:103: error: syntax error before >> ‘*’ token >> rpy/rinterface/array.c:104: warning: function declaration >> isn’t a >> prototype >> rpy/rinterface/array.c: In function ‘array_struct_get’: >> rpy/rinterface/array.c:105: warning: implicit declaration of function >> ‘RPY_SEXP’ >> rpy/rinterface/array.c:105: error: ‘self’ undeclared >> (first use in >> this function) >> rpy/rinterface/array.c:105: error: (Each undeclared identifier is >> reported only once >> rpy/rinterface/array.c:105: error: for each function it appears in.) >> rpy/rinterface/array.c:105: warning: initialization makes pointer >> from >> integer without a cast >> lipo: can't open input file: /var/folders/S0/S0L2IJNaGdqPs3a4cwhVck++ >> +TI/-Tmp-//ccOoqfmp.out (No such file or directory) >> <<< >> >> Any help to sort this out would be appreciated. > > > > ------------------------------ > > Message: 3 > Date: Wed, 03 Sep 2008 07:28:54 +0000 > From: [EMAIL PROTECTED] > Subject: [Rpy] SF.net SVN: rpy:[649] branches/rpy_nextgen > To: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=UTF-8 > > Revision: 649 > http://rpy.svn.sourceforge.net/rpy/?rev=649&view=rev > Author: lgautier > Date: 2008-09-03 07:28:53 +0000 (Wed, 03 Sep 2008) > > Log Message: > ----------- > tentative fix for the external (non-R) blas or lapack libraries > (someone to test ?) > > Modified Paths: > -------------- > branches/rpy_nextgen/NEWS > branches/rpy_nextgen/setup.py > > Modified: branches/rpy_nextgen/NEWS > =================================================================== > --- branches/rpy_nextgen/NEWS 2008-09-02 17:48:47 UTC (rev 648) > +++ branches/rpy_nextgen/NEWS 2008-09-03 07:28:53 UTC (rev 649) > @@ -31,9 +31,11 @@ > > - proper reference counting when handling, and > deleting, :attr:`Sexp.__sexp__` generated CObjects > > -- get properly the include directories (no matter where they are) > #bug report and fix adapted from Robert Nuske > +- setup.py: get properly the include directories (no matter where > they are) #bug report and fix adapted from Robert Nuske > > +- setup.py: link to external lapack or blas library when relevant > > + > Release 2.0.0a3 > =============== > > > Modified: branches/rpy_nextgen/setup.py > =================================================================== > --- branches/rpy_nextgen/setup.py 2008-09-02 17:48:47 UTC (rev 648) > +++ branches/rpy_nextgen/setup.py 2008-09-03 07:28:53 UTC (rev 649) > @@ -113,7 +113,7 @@ > os.path.join('rpy', 'rinterface', 'rinterface.c')], > include_dirs = include_dirs + > [os.path.join('rpy', 'rinterface'),], > - libraries = ['R', 'Rlapack', 'Rblas'], > + libraries = ['R', ], > library_dirs = r_libs, > define_macros = define_macros, > runtime_library_dirs = r_libs, > > > This was sent by the SourceForge.net collaborative development > platform, the world's largest Open Source development site. > > > > ------------------------------ > > Message: 4 > Date: Wed, 3 Sep 2008 09:49:04 +0200 > From: Robert Nuske <[EMAIL PROTECTED]> > Subject: Re: [Rpy] problem installing rpy2 > To: laurent <[EMAIL PROTECTED]>, rpy-list@lists.sourceforge.net > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="utf-8" > > Hi laurent, > > I just opend my mail-program to write you that I had to > delete 'Rlapack', 'Rblas' to make the setup.py finally work, when I > saw the > note about your change in svn. > > I checked out revision 649. > And yes, I can confirm it works now ;-) > > I was wondering about line 107 in setup.py > include_dirs = [x.lstrip('-I') for x in include_dirs] > is there a reason to keep duplicate information about the path to > the include > dir? Or could there resonably be more than one include dir? > > cheers, > robert > >>>>> I found them here: >>>>> /usr/share/R/include/Rdefines.h >>>>> /usr/share/R/include/Rinternals.h >>>>> /usr/share/R/include/R.h >>>> >>>> I may have seen that one problem mentioned earlier to the list. >>> >>> me to, but can't find it now >>> >>>> The location of R's include files is seemingly a bit too exotic >>>> for the >>>> disutils script. >>> >>> they were placed there by the debian package >>> >>>> The setup.py script expects them to be in ${RHOME}/include >>>> (RHOME being the outcome of running 'R RHOME'). >>> >>> by googeling R_INCLUDE_DIR I found that it is not recommended to >>> rely on >>> ${RHOME}/include >>> >>> eg. >>> http://www.nabble.com/Bug-354775%3A-r-base-core%3A-R-CMD-config-doesn%27t >>> -reflect-new-file-locations-tp3175446p3175720.html >>> >>>> There is currently no other way around that than either >>>> - edit setup.py >>>> - copy or link the headers. >>> >>> one way to get the include dirs >>> R CMD echo $R_INCLUDE_DIR >>> >>> but the recommed way of finding the include dirs seems to be: >>> R CMD config --cppflags >>> >>> on my system this returns >>> -I/usr/share/R/include -I/usr/share/R/include >>> >>> but I can't use it with get_rconfig, since get_rconfig checks for - >>> l/-L >>> and raises an ecxecption otherwise, more or less >> >> get_rconfig is very picky before returning anything (that makes it >> return generally useful error reports when failing). >> Now it nows about '^-I'. >> >>> If I hardcode the include dir in setup.py it finds the headers, >>> but stops >>> with: >>> >>> [EMAIL PROTECTED]:/usr/local/src/rpy_nextgen$ python setup.py install >>> running install >>> running build >>> running build_py >>> running build_ext >>> building 'rpy2.rinterface.rinterface' extension >>> gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions >>> build/temp.linux-i686-2.5/rpy/rinterface/array.o >>> build/temp.linux-i686-2.5/rpy/rinterface/r_utils.o >>> build/temp.linux-i686-2.5/rpy/rinterface/rinterface.o -L/usr/lib/R/ >>> lib >>> -L/usr/lib/R/modules -Wl,-R/usr/lib/R/lib -Wl,-R/usr/lib/R/modules >>> -lR >>> -lRlapack -lRblas -o >>> build/lib.linux-i686-2.5/rpy2/rinterface/rinterface.so -L/usr/lib/ >>> R/lib >>> -lR -llapack -lblas /usr/bin/ld: cannot find -lRlapack >> >> Is this still happening with the last fix committed to SVN ? >> >> >> >> >> >> L. >> >>> collect2: ld returned 1 exit status >>> error: command 'gcc' failed with exit status 1 >>> >>> >>> cheers, >>> robert > > > > -- > Robert Nuske > Department of Ecoinformatics, > Biometrics & Forest Growth > > Buesgenweg 4 > 37077 Goettingen > GERMANY > > Phone: +49-551-39-22362 > Fax : +49-551-39-3465 > > > > ------------------------------ > > Message: 5 > Date: Wed, 03 Sep 2008 10:14:28 +0200 > From: laurent <[EMAIL PROTECTED]> > Subject: Re: [Rpy] problem installing rpy2 > To: [EMAIL PROTECTED] > Cc: rpy-list@lists.sourceforge.net > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain > > On Wed, 2008-09-03 at 09:49 +0200, Robert Nuske wrote: >> Hi laurent, >> >> I just opend my mail-program to write you that I had to >> delete 'Rlapack', 'Rblas' to make the setup.py finally work, when I >> saw the >> note about your change in svn. >> >> I checked out revision 649. >> And yes, I can confirm it works now ;-) >> >> I was wondering about line 107 in setup.py >> include_dirs = [x.lstrip('-I') for x in include_dirs] >> is there a reason to keep duplicate information about the path to >> the include >> dir? Or could there resonably be more than one include dir? > > R CMD config --cppflags returned two paths here (twice the same, > now that you point it out). > I went for the safest and make sure all are included. > >> cheers, >> robert >> >>>>>> I found them here: >>>>>> /usr/share/R/include/Rdefines.h >>>>>> /usr/share/R/include/Rinternals.h >>>>>> /usr/share/R/include/R.h >>>>> >>>>> I may have seen that one problem mentioned earlier to the list. >>>> >>>> me to, but can't find it now >>>> >>>>> The location of R's include files is seemingly a bit too exotic >>>>> for the >>>>> disutils script. >>>> >>>> they were placed there by the debian package >>>> >>>>> The setup.py script expects them to be in ${RHOME}/include >>>>> (RHOME being the outcome of running 'R RHOME'). >>>> >>>> by googeling R_INCLUDE_DIR I found that it is not recommended to >>>> rely on >>>> ${RHOME}/include >>>> >>>> eg. >>>> http://www.nabble.com/Bug-354775%3A-r-base-core%3A-R-CMD-config-doesn%27t >>>> -reflect-new-file-locations-tp3175446p3175720.html >>>> >>>>> There is currently no other way around that than either >>>>> - edit setup.py >>>>> - copy or link the headers. >>>> >>>> one way to get the include dirs >>>> R CMD echo $R_INCLUDE_DIR >>>> >>>> but the recommed way of finding the include dirs seems to be: >>>> R CMD config --cppflags >>>> >>>> on my system this returns >>>> -I/usr/share/R/include -I/usr/share/R/include >>>> >>>> but I can't use it with get_rconfig, since get_rconfig checks for >>>> -l/-L >>>> and raises an ecxecption otherwise, more or less >>> >>> get_rconfig is very picky before returning anything (that makes it >>> return generally useful error reports when failing). >>> Now it nows about '^-I'. >>> >>>> If I hardcode the include dir in setup.py it finds the headers, >>>> but stops >>>> with: >>>> >>>> [EMAIL PROTECTED]:/usr/local/src/rpy_nextgen$ python setup.py install >>>> running install >>>> running build >>>> running build_py >>>> running build_ext >>>> building 'rpy2.rinterface.rinterface' extension >>>> gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions >>>> build/temp.linux-i686-2.5/rpy/rinterface/array.o >>>> build/temp.linux-i686-2.5/rpy/rinterface/r_utils.o >>>> build/temp.linux-i686-2.5/rpy/rinterface/rinterface.o -L/usr/lib/ >>>> R/lib >>>> -L/usr/lib/R/modules -Wl,-R/usr/lib/R/lib -Wl,-R/usr/lib/R/ >>>> modules -lR >>>> -lRlapack -lRblas -o >>>> build/lib.linux-i686-2.5/rpy2/rinterface/rinterface.so -L/usr/lib/ >>>> R/lib >>>> -lR -llapack -lblas /usr/bin/ld: cannot find -lRlapack >>> >>> Is this still happening with the last fix committed to SVN ? >>> >>> >>> >>> >>> >>> L. >>> >>>> collect2: ld returned 1 exit status >>>> error: command 'gcc' failed with exit status 1 >>>> >>>> >>>> cheers, >>>> robert >> >> >> > > > > > ------------------------------ > > Message: 6 > Date: Wed, 03 Sep 2008 11:40:13 +0200 > From: laurent <[EMAIL PROTECTED]> > Subject: Re: [Rpy] How to install rpy on 64bit machine? > To: Hyunchul Kim <[EMAIL PROTECTED]> > Cc: "RPy help, support and design discussion list" > <rpy-list@lists.sourceforge.net> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain > > Checking what is the first error message seems to be helpful. > (headers for Python appear to be missing) > > On Wed, 2008-09-03 at 18:35 +0900, Hyunchul Kim wrote: >> In file included from src/rpymodule2070.c:51: >> src/RPy.h:56:20: error: Python.h: No such file or directory >> In file included from src/RPy.h:57, >> from src/rpymodule2070.c:51: > > > > > ------------------------------ > > ------------------------------------------------------------------------- > 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 > > > End of rpy-list Digest, Vol 28, Issue 4 > *************************************** ------------------------------------------------------------------------- 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
