Hi Developers,
The alpha, compiles successfully, but it is failing make check-all (on
two seperate machines, both FreeBSD 6.1).
Here is the version string:
platform i386-unknown-freebsd6.1
arch i386
os freebsd6.1
system i386, freebsd6.1
status alpha
ma
On Mon, 27 Mar 2006, Jussi T Lindgren wrote:
> On Mon, 27 Mar 2006, Prof Brian Ripley wrote:
>
>> Not reproducible for me (and do you really think that something as simple as
>> this would not have been found on x86_64 long before now?)
>> This is almost certainly caused by your use of an inapprop
Hi, people. Here is a transcript of a "R --vanilla" session:
==>
R : Copyright 2005, The R Foundation for Statistical Computing
Version 2.2.1 (2005-12-20 r36812)
ISBN 3-900051-07-0
R est un logiciel libre livré sans AUCUNE GA
Full_Name: D Kreil
Version: R 2.2.1 (2005-12-20).
OS: Linux, Fedora FC4
Submission from: (NULL) (62.178.15.60)
sink("filename",split=T);
cat("sometext\n");
for (...) {
cat(some terms);
}
reproducibly gives a segmentation fault. No other problems with this
installation.
Removing the split=T fix
On Mon, 27 Mar 2006, Prof Brian Ripley wrote:
> Not reproducible for me (and do you really think that something as simple as
> this would not have been found on x86_64 long before now?)
> This is almost certainly caused by your use of an inappropriate external BLAS.
> Something has probably been c
Not reproducible for me (and do you really think that something as simple
as this would not have been found on x86_64 long before now?)
This is almost certainly caused by your use of an inappropriate external
BLAS. Something has probably been compiled for a different processor than
the one you
Matrix inner product seems to crash R2.2.1 on a 64bit arch.
More precisely, the crash happens atleast if the matrix is
non-square. The bug can be reproduced (atleast here) with
bash$ bin/R
> X<-matrix(data=0,nrow=100,ncol=10);
> mat<-X%*%t(X);
Illegal instruction
bash$
The crash doesnt happen
On Mon, 27 Mar 2006, Michael Dondrup wrote:
> Thank you very much,
> Sorry for bothering again, but how about this:
>
>> assignInNamespace('system',function(...)stop('No system!'),'base')
>> system()
> Error in system() : No system!
>> base::system()
> Error in base::system() : No system!
>> detac
Thank you very much,
Sorry for bothering again, but how about this:
> assignInNamespace('system',function(...)stop('No system!'),'base')
> system()
Error in system() : No system!
> base::system()
Error in base::system() : No system!
> detach(package:utils) # no way back?
I guess there is a wa
Full_Name: TOBY MARTHEWS
Version: 2.1.1
OS: Windows XP
Submission from: (NULL) (139.133.7.38)
I think you should have better examples on the ?plot man page, if you don't mind
me saying. Can I suggest something like this, which would probably stop so many
emails to the R help about how to put on e
Hi Steve,
Are you sure you want a bundle? If you are writing your own package
Foo that depends on two pacakges already available via CRAN, then all
you need to do is list those two pacakges in the Depends field of your
package's DESCRIPTION file.
This will give you the automatic downloading of F
Peter Dalgaard <[EMAIL PROTECTED]> writes:
> The release of version 2.3.0 has been scheduled for April 24, 2006.
>
> The first alpha release should be available later today, once I have
> reviewed the build scripts.
Done. The first version is now sitting in
http://biostat.ku.dk/~pd/R-pre
Fu
Steve Su wrote:
> Dear All,
>
>
>
> What is the easiest way to create a package bundle in R? I have three
> packages I would like to group together in which one package will
> depends on three others. It looks like from
>
> http://tolstoy.newcastle.edu.au/R/help/01a/0284.html, all that is
> r
"Henrik Bengtsson" <[EMAIL PROTECTED]> writes:
> Hi,
>
> I'm troubleshooting some native code on Windows that very occationally
> (and semi-randomly) crashes R. Already looked at "everything", I just
> want to double check that it is safe to UNPROTECT() allocated
> variables as soon as they are
The release of version 2.3.0 has been scheduled for April 24, 2006.
The first alpha release should be available later today, once I have
reviewed the build scripts.
The detailed release schedule is as follows
March 27:
Declare start of release process. The build process is assumed to
On 3/27/2006 1:47 AM, Martin Maechler wrote:
> [from a semi-private diversion of the R-devel thread ]
>
>> "Duncan" == Duncan Murdoch <[EMAIL PROTECTED]>
>> on Sat, 25 Mar 2006 12:28:30 -0500 writes:
>
> Duncan> On 3/25/2006 11:30 AM, Martin Maechler wrote:
> >> Hi Duncan,
>
Hi,
I'm troubleshooting some native code on Windows that very occationally
(and semi-randomly) crashes R. Already looked at "everything", I just
want to double check that it is safe to UNPROTECT() allocated
variables as soon as they are assigned to, say, a PROTECTed list.
>From (R v2.3.0) Sectio
Full_Name: TOBY MARTHEWS
Version: 2.2.1
OS: Windows XP
Submission from: (NULL) (139.133.7.37)
Just a small one, but it did trip me up today. On the ?symbols man page the
following paragraph:
inches: If 'inches' is 'FALSE', the units are taken to be those of
the x axis...
should say:
G'day Brian,
> "BDR" == Prof Brian Ripley <[EMAIL PROTECTED]> writes:
BDR> The proposed fix regretably will not work, since one can do
BDR> things like
BDR> library(MASS)
BDR> prcomp(~ dist + dist:climb, hills)
Yes, I had the impression that this would work with the current
v
On Mon, 27 Mar 2006, Michael Dondrup wrote:
> Hi,
> is there a way to restrict the set of admissible functions for an eval()
> statement to a possibly 'safe' set, excluding all potentially dangerous
> functions like 'system', 'open', etc.(like, for instance, in the 'Safe'
> module for Perl)?
In s
Hi,
is there a way to restrict the set of admissible functions for an eval()
statement to a possibly 'safe' set, excluding all potentially dangerous
functions like 'system', 'open', etc.(like, for instance, in the 'Safe'
module for Perl)?
The background for this question is, that this would be
21 matches
Mail list logo
