[Rcpp-devel] RcppEigen needs 1GB memory to compile
djsamperi at gmail.com
Sun Dec 8 20:47:34 CET 2013
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 ones, thus the need for a
huge amount of memory in some cases. The suggestion to drop -pipe
might be helpful since it pushes more of the resource use from memory
On Mon, Dec 2, 2013 at 2:52 PM, Douglas Bates <bates at stat.wisc.edu> wrote:
> 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
> packages that use RcppEigen only use the headers, not the DLL file, it
> doesn't matter if the symbols are stripped.
> On Mon, Dec 2, 2013 at 1:31 PM, Dirk Eddelbuettel <edd at debian.org> wrote:
>> On 2 December 2013 at 11:17, Jeroen Ooms wrote:
>> | I noticed that RcppEigen fails to install on my servers because it
>> | 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? A short simulation:
>> I have had to resort to similar tricks on some smaller architecture when
>> autobuilding demanding Debian packages. Try -O0 -g0 for a start.
>> Or if you need a smile, this still holds:
>> Dirk Eddelbuettel | edd at debian.org | http://dirk.eddelbuettel.com
>> Rcpp-devel mailing list
>> Rcpp-devel at lists.r-forge.r-project.org
> Rcpp-devel mailing list
> Rcpp-devel at lists.r-forge.r-project.org
More information about the Rcpp-devel