On 12-04-17 2:19 AM, Henrik Bengtsson wrote:
'R --debug' and 'Rterm --debug' crash R on Windows. Indeed, --debug
is not a documented command line option, but it still causes a crash.
This occurs with R v2.15.0 patched and R devel - both from 2012-04-09 (r58947).
What do you mean by crash?
On Tue, Apr 17, 2012 at 1:01 AM, Renaud Gaujoux
ren...@mancala.cbio.uct.ac.za wrote:
Hi,
when I run R CMD check with flag --as-cran, the process hangs at stage:
* checking CRAN incoming feasibility ...
Doesn't it time-out eventually? I'm not behind a proxy but when I've
been running 'R CMD
I can reproduce the R for Windows terminal front-end has stopped
working with both R-2.14.1 and R-2.13.0 (i386), and get the hang but
not crash with both of the x64 binaries for those versions.
On 4/17/2012 2:01 PM, Henrik Bengtsson wrote:
I really meant crash and left my report short
Hi,
I'd like to compile the NAMESPACE file from a template where things
such as S3method() statements are automatically inserted based on code
inspection, because doing it by hand is too error prone. I am
currently generating a NAMESPACE file this way which I copy to my
package root, but I'd
On 12-04-17 5:24 PM, andre zege wrote:
I am unable to compile R-2.15.0 source. I configured it without problems
with options that i used many times before
./configure --prefix=/home/andre/R-2.15.0
--enable-byte-compiled-packages=no --with-tcltk --enable-R-shlib=yes
Then when i started making
Hi Henrik,
I am sure it would time out indeed. I am fine with time out due to poor
connection, but get a bit frustrated if my connection is fine and timeout
occurs because proxy settings are not read. All the more if I have to run
R CMD check multiple times and wait for the timeout.
But the
