Thanks. One of the first things I do when building libbitcoin on our
cheaper VM's is to modify the $PARALLEL variable to stay within our
RAM limits. I'm glad to know I'm not the only one with this problem,
and that the solution is now officially supported!

-William

On Wed, Jan 20, 2016 at 4:08 PM, Eric Voskuil <eric@???> wrote:
> Thanks. I've modified the install script generation to incorporate
> consideration of a shell-defined $PARALLEL environment variable:
>
> https://github.com/libbitcoin/libbitcoin-build/blob/version2/templates/gsl.install.sh#L185
>
> This will eventually make its way into the various repo install.sh
> scripts. If this variable is defined it will override core detection. We
> could alternatively make this a script command line option, but this was
> the simplest quick fix.
>
> e
>
> On 01/20/2016 04:29 AM, mlmikael wrote:
>> Hi everyone,
>>
>> Currently, the ./install.sh-script is hardwired to run as many C
>> compiler instances as there are CPU cores, see:
>>
>> https://github.com/libbitcoin/libbitcoin-node/blob/a1b661c71bae82c1df4283b50c680a915a057563/install.sh#L65-L74
>>
>>
>>
>> Since LibBitcoin is a general purpose library, I think it's fair to say
>> that its build process should be set up in a way that will run on crappy
>> hardware too.
>>
>> Currently, if you have 4GB RAM and 16 CPU cores, the build process will
>> likely kill your machine. Also 2GB RAM and 4 cores.
>>
>> So for users not to need to patch the install.sh script, I want to check
>> what you think about the idea, that,
>>
>>
>> There would be an argument to ./install.sh for overriding how many CPU
>> cores are used, just like "make" has a "-j" argument.
>>
>> Thoughts?
>
>
> _______________________________________________
> Libbitcoin mailing list
> Libbitcoin@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin
>