You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building the libadalang_tools create I saw that I nearly maxed out my 12GB of RAM and 4GB of swap, so I had to add some additional gigs of swap to avoid the same OOM issue that caused me issues when building the ALS. That last issue made me aware of the -J switch for gprbuild, to limit the number of processes:
-j<num> Use <num> processes to compile, bind, and link
-jc<num> Use <num> processes to compile
-jb<num> Use <num> processes to bind
-jl<num> Use <num> processes to link
Some searching made me find the option of adding -- to pass options to gprbuild when doing alr build. alr build -- -J4 should limit the number of processes to 4, AFAIK, but is it possible to achieve the same when doing alr install some_exe? Maybe it could be a global setting one could set or an environment variable?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When building the libadalang_tools create I saw that I nearly maxed out my 12GB of RAM and 4GB of swap, so I had to add some additional gigs of swap to avoid the same OOM issue that caused me issues when building the ALS. That last issue made me aware of the
-Jswitch forgprbuild, to limit the number of processes:Some searching made me find the option of adding
--to pass options togprbuildwhen doingalr build.alr build -- -J4should limit the number of processes to 4, AFAIK, but is it possible to achieve the same when doingalr install some_exe? Maybe it could be a global setting one could set or an environment variable?Beta Was this translation helpful? Give feedback.
All reactions