Is this really the important thing? Seems like -g0 saves disk space, not memory?
(Loading the symbols into a debugger may require lots of memory, but that
is not the issue here.)
Header-only C++ packages require the compiler to effectively process one
huge source file instead of a bunch of smaller
On 3 December 2013 at 08:36, Kasper Daniel Hansen wrote:
| Could I suggest taking all of this example code and move it into something
like
| RcppExample or RcppTesting, which RcppXX could suggest and use for testing.
| This will have the benefit of having a testing package that also does the
| o
Could I suggest taking all of this example code and move it into something
like RcppExample or RcppTesting, which RcppXX could suggest and use for
testing. This will have the benefit of having a testing package that also
does the outside package linking. If this is done as a split of the basic
pa
On 3 December 2013 at 12:51, Romain Francois wrote:
| Le 03/12/2013 12:38, Dirk Eddelbuettel a écrit :
| > And headers-only wasn't an option when fastLm() was first set up.
|
| Of course it was. We could definitely have RcppEigen header only even
| with CRAN not header only Rcpp.
Point taken bu
Le 03/12/2013 12:38, Dirk Eddelbuettel a écrit :
On 2 December 2013 at 14:43, Douglas Bates wrote:
| On Mon, Dec 2, 2013 at 2:20 PM, Dirk Eddelbuettel wrote:
| Do you think we should move fastLm out?
|
|
| And face the "Wrath of Achim" for removing a function that is described in a
| JSS pa
On 2 December 2013 at 14:43, Douglas Bates wrote:
| On Mon, Dec 2, 2013 at 2:20 PM, Dirk Eddelbuettel wrote:
| Do you think we should move fastLm out?
|
|
| And face the "Wrath of Achim" for removing a function that is described in a
| JSS paper?
We could add a 'Suggests: RcppEigenFastLm'
Le 02/12/2013 21:43, Douglas Bates a écrit :
On Mon, Dec 2, 2013 at 2:20 PM, Dirk Eddelbuettel mailto:[email protected]>> wrote:
On 2 December 2013 at 13:52, Douglas Bates wrote:
| The important thing is to use the -g0 flag. Even though RcppEigen
is a
Right.
And for the op
On Mon, Dec 2, 2013 at 2:20 PM, Dirk Eddelbuettel wrote:
>
> On 2 December 2013 at 13:52, Douglas Bates wrote:
> | The important thing is to use the -g0 flag. Even though RcppEigen is a
>
> Right.
>
> And for the opencpu server deployment, you may want to edit the -g out
> /etc/R/Makeconf as we
On 2 December 2013 at 13:52, Douglas Bates wrote:
| The important thing is to use the -g0 flag. Even though RcppEigen is a
Right.
And for the opencpu server deployment, you may want to edit the -g out
/etc/R/Makeconf as well. As I recall, there was an r-devel thread in which
the desire to ove
The important thing is to use the -g0 flag. Even though RcppEigen is a
header-only package we include an example R function fastlm. If you leave
the symbols in the DLL file you get a massive library size whereas
stripping the symbols provides you with a much smaller file size. And
because packag
On 2 December 2013 at 11:21, Kevin Ushey wrote:
| Try removing -pipe: see e.g.
| http://gcc.gnu.org/onlinedocs/gcc/Overall-Options.html#Overall-Options,
| at -pipe.
Very good suggestion. That is "my fault" too via the default Debian/Ubuntu
setup:
edd@max:~$ grep pipe /etc/R/Makeconf
# configur
On 2 December 2013 at 11:17, Jeroen Ooms wrote:
| I noticed that RcppEigen fails to install on my servers because it requires
| more than 1gb of memory to compile. Is this expected? Are there any flags or
Yes. It also falls over on R-Forge.
| options I could set to trade of some memory for cpu?
Try removing -pipe: see e.g.
http://gcc.gnu.org/onlinedocs/gcc/Overall-Options.html#Overall-Options,
at -pipe.
On Mon, Dec 2, 2013 at 11:17 AM, Jeroen Ooms wrote:
> I noticed that RcppEigen fails to install on my servers because it requires
> more than 1gb of memory to compile. Is this expected?
13 matches
Mail list logo
