Re: [IBMiOSS] gmake: *** virtual memory exhausted. Stop.

"OpenSource" <opensource-bounces@xxxxxxxxxxxx> wrote on 07/20/2016
12:42:30 PM:

From: Aaron Bartell <aaronbartell@xxxxxxxxx>
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
Date: 07/20/2016 12:43 PM
Subject: Re: [IBMiOSS] gmake: *** virtual memory exhausted. Stop.
Sent by: "OpenSource" <opensource-bounces@xxxxxxxxxxxx>

I would think then you wouldn't have to worry much about updates to

Node

itself.

Multiple versions are still necessary because language features are
changing. For example, I might install the latest PTF with the new

Node.js

version but I don't want to blindly accept the PTF won't cause issues

with

my existing app. I would instead want to run all of my unit tests

against

the new version without losing the old version. There's just too many
things that could go wrong (i.e. a deprecated API warning coming to full
fruition and is finally removed).

Right, but don't these sort of changes only happen going from eg. 1.x ->
2.x (in OPS these would be in separate options).

I wouldn't expect Node 0.12.10 -> 0.12.11 to be a problematic upgrade, but
maybe I'm naive.