Thanks for the link, Prof. Ripley.
> What I suspect is happening is that there is a link command starting with
> 'g++' that is too long.
> One useful ref: http://www.in-ulm.de/~mascheck/various/argmax
interesting...
on my system:
[EMAIL PROTECTED] src]$ getconf ARG_MAX
131072
[EMAIL PROTECTED]
On Tue, 9 Dec 2008, Whit Armstrong wrote:
Thanks for the suggestion. this package was building successfully
until I split it up into smaller files.
(there are 4489 files in the src directory)
I suspect it's a hard limit in the linux kernel.
http://www.linuxjournal.com/article/6060
since R C
Thanks for the suggestion. this package was building successfully
until I split it up into smaller files.
(there are 4489 files in the src directory)
I suspect it's a hard limit in the linux kernel.
http://www.linuxjournal.com/article/6060
since R CMD check is generating the actual commands th
Just a suggestion. I googled for your error message you got e.g. "make
... error 127" and I got
Yeah, error 127 indicates that make can't find a program that it needs to
run a command. My guess would be that she doesn't have g++ installed
(some distributions package it separately from gcc so it
The message (it is not even a warning) is harmless. The change is
documented in the NEWS file, and is useful for some packages (Matrix as I
recall).
On Tue, 9 Dec 2008, Josef Leydold wrote:
Hi,
I wonder about the reason for the following lines:
$ diff ~/local/lib64/R/bin/build /usr/lib64/R/
I love xargs for all kinds of stuff, but I really don't want to write
my own configure script.
looks like simple solution is to recombine into one big source file
rather than splitting each function out. pita...
-Whit
On Tue, Dec 9, 2008 at 4:23 PM, Jeff Ryan <[EMAIL PROTECTED]> wrote:
> Never
Hi,
I wonder about the reason for the following lines:
$ diff ~/local/lib64/R/bin/build /usr/lib64/R/bin/build
40c40
< my $revision = ' $Rev: 46832 $ ';
---
> my $revision = ' $Rev: 45803 $ ';
576,579d570
< if(-r "Makevars") {
< $makefiles .= " -f Makevars";
<
Never used, but I seem to recall that this was good for that:
http://en.wikipedia.org/wiki/Xargs
Jeff
On Tue, Dec 9, 2008 at 3:13 PM, Whit Armstrong <[EMAIL PROTECTED]> wrote:
> Since, gcc was using upwards of 2gb of ram to compile my package, I
> just split all the functions into individual fil
Since, gcc was using upwards of 2gb of ram to compile my package, I
just split all the functions into individual files.
I guess I'm too clever for myself, because now I get hit with the
"Argument list too long" error.
Is there a way to deal with this aside from writing my own configure
script (wh
No idea,
perhaps add some print statements in teh perl code that executes the
checks and see why it does not jump in.
uwe
Andy Bunn wrote:
-Original Message-
From: Uwe Ligges [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 09, 2008 2:03 AM
To: Andy Bunn
Cc: r-devel@r-project.org
This is a shot in the dark, but I noticed your PATH contains spaces in
the paths to HTML Help and MiKTeX. The R Install & Admin manual
explicitly says not to paths with spaces. If anything, it won't hurt
to make this correction.
HTH,
Josh
--
http://quantemplation.blogspot.com
On Tue, Dec 9, 2
> -Original Message-
> From: Uwe Ligges [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 09, 2008 2:03 AM
> To: Andy Bunn
> Cc: r-devel@r-project.org
> Subject: Re: [Rd] R CMD check not running examples under Windows
>
> My suggestion is to submit the package to the win-builder service
My suggestion is to submit the package to the win-builder service and
look whether that one checks your example, then you know if it is the
package or your setup that causes the problem.
Best,
Uwe Ligges
Andy Bunn wrote:
All,
I have a fresh build of R 2.8.0 from source on Windows XP using
All,
I have a fresh build of R 2.8.0 from source on Windows XP using the latest
Rtools binary (Rtools29.exe). All appears to be well with the install and make
check-all exits cleanly. However, when running R CMD check mypkg the program
jumps from checking for non-ASCII to checking the PDF ver
14 matches
Mail list logo