Re: [Rd] Cross-compile errors under R-2.4.0 and R-2.4.1

From: Daniel Berg <daniel_at_danielberg.no>
Date: Fri 19 Jan 2007 - 19:46:37 GMT

Thank you so much for your great answers, and I apologize for using obsolete versions and not being up to date on all the posts.

My native linux R is indeed R-2.3.1 which was also the version for which I successfully cross-compiled. When trying to cross-compile for 2.4.0 and 2.4.1 I was not successful.

//Daniel

On 1/19/07, Hin-Tak Leung <hin-tak.leung@cimr.cam.ac.uk> wrote:
> Prof Brian Ripley wrote:
> > The 2.4.0 issue has been well documented only last week, in the thread
> >
> > https://stat.ethz.ch/pipermail/r-help/2007-January/123303.html
> >
> > as well as in an answer I had already posted.
> >
> > I am almost certain the issue for 2.4.1 is user error. Remember you need
> > to set in MkRules
> >
> > ## =================== cross-compilation settings =================
> >
> > ...
> >
> > # path (possibly full path) to same version of R on the host system
> > # R_EXE=R
> >
> > R 2.4.1 does have seq_along, so it must not be the same version.
>
> I feel that one point in the cross-build related documentation
> wasn't emphasized enough, and may have caused this sort of error
> when one tries to build multiple versions of R: the version of
> native R used *must* match the version of cross R one intends to build.
>
> The user mentioned that he tried building R 2.3.1, 2.4.0 and 2.4.1 ;
> the only way it would work successfully would be that he also has
> linux native R of all three of those versions.
>
> HTL
>
> > On Fri, 19 Jan 2007, Daniel Berg wrote:
> >
> >> Dear all,
> >>
> >> I already posted a question regarding this to an existing thread:
> >> http://tolstoy.newcastle.edu.au/R/e2/devel/06/10/0852.html#start
> >>
> >> I apologize for the double posting but I have some further information
> >> that might be illuminating.
> >>
> >> I am trying to cross-compile my R-package under ubuntu linux, kernel
> >> 2.6.17-10-generic, on an IBM T60.
> >>
> >> I am following the suggested steps in
> >> http://cran.r-project.org/doc/contrib/cross-build.pdf
> >>
> >> I have tried changing R = R-x.x.x (2.3.1, 2.4.0 and 2.4.1) in
> >> http://cran.ii.uib.no/doc/contrib/Makefile-rcb
> >>
> >> 1) For R-2.3.1 everything works fine
> >> 2) For R-2.4.0 I receive the following error messages from 'make R':
> >>
> >> ../extra/pcre/libpcre.a(pcre_dfa_exec.o):pcre_dfa_exec.c:(.text+0x1f2a):
> >> more undefined references to `__pcre_ucp_findprop' follow
> >> collect2: ld returned 1 exit status
> >> make[4]: *** [R.dll] Error 1
> >> make[3]: *** [../../bin/R.dll] Error 2
> >> make[2]: *** [rbuild] Error 2
> >> make[1]: *** [all] Error 2
> >> make[1]: Leaving directory
> >>
> >> There is already a post that seems to address the same error:
> >> http://tolstoy.newcastle.edu.au/R/e2/devel/06/10/0852.html#start
> >>
> >> However, I have tried the suggestions there with no further success
> >> and I am awaiting further instructions before pursuing that solution.
> >>
> >> 3) For R-2.4.1 I receive the following error message from 'make R',
> >> under 'Making package tools':
> >>
> >> preparing package tools for lazy loading
> >> Error in makeLazyLoadDB(ns, dbbase) : could not find function "seq_along"
> >> Execution halted
> >>
> >>
> >> Hope this is illuminating and that the 'bugs', whether it is in R or
> >> in PCRE, can be resolved for the next release, this would be highly
> >> appreciated. Meanwhile, any suggestions as to how I can cross-compile
> >> successfully under R-2.4.1 are most welcome.
> >>
> >> Best wishes,
> >> Daniel Berg
> >>
> >
>
>
>

-- 
danielberg.no

______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Received on Sat Jan 20 07:14:37 2007

Archive maintained by Robert King, hosted by the discipline of statistics at the University of Newcastle, Australia.
Archive generated by hypermail 2.1.8, at Fri 19 Jan 2007 - 21:31:10 GMT.

Mailing list information is available at https://stat.ethz.ch/mailman/listinfo/r-devel. Please read the posting guide before posting to the list.