Skip to content

Potential recompilation of certain packages

4 messages · A.J. Rossini, Peter Dalgaard, Duncan Temple Lang

#
This applies to people working with the up-to-the-minute source taken
directly or indirectly from the CVS repository. Changes to the
mechanism for registering native (C and Fortran) routines in
DLLs/shared libraries and the package level data structures mean that
you will have to recompile any package that uses this approach to
exporting routines. These include all of the MASS packages, but few
others (yet :-)). No changes to those packages are necessary, just a
simple re-installation.

The changes allow one to specify types for the parameter of the
routines, and also whether they contain useful output values when
returned to R. These have the potential to avoid unecessary copying
and are more robust to errors in types passed to the routines.

Sorry for any inconvenience.

 Duncan
#
And the obvious question, given the timing, 
"does this apply to 1.5.1?"

best,
-tony
duncan> This applies to people working with the up-to-the-minute
    duncan> source taken directly or indirectly from the CVS
    duncan> repository. Changes to the mechanism for registering
    duncan> native (C and Fortran) routines in DLLs/shared libraries
    duncan> and the package level data structures mean that you will
    duncan> have to recompile any package that uses this approach to
    duncan> exporting routines. These include all of the MASS
    duncan> packages, but few others (yet :-)). No changes to those
    duncan> packages are necessary, just a simple re-installation.

    duncan> The changes allow one to specify types for the parameter
    duncan> of the routines, and also whether they contain useful
    duncan> output values when returned to R. These have the potential
    duncan> to avoid unecessary copying and are more robust to errors
    duncan> in types passed to the routines.
#
rossini@blindglobe.net (A.J. Rossini) writes:
No. Bleeding edge, i.e., what might become 1.6.0, only. (Or DTL would
have made himself *very* unpopular.)

  
    
#
A.J. Rossini wrote:
Good question. No, it should not have anything to do with that.  And,
my guess is that you will notice it immediately on calling library()
on any of the affected packages with a large seg-fault. At least its
dramatic :-)

 D.
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-devel-request@stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._