| 1 |
On Wed, 2021-04-07 at 22:15 +0200, karl@××××××××.se wrote: |
| 2 |
> |
| 3 |
> yea, it was a try to make c++ programs to behave under changing |
| 4 |
> compiler and library situations. Seems that some such programs |
| 5 |
> don't want to be built statically so they break whenever some "random" |
| 6 |
> lib changes. |
| 7 |
> |
| 8 |
|
| 9 |
That's my best guess as to why your build is using so much more RAM. |
| 10 |
Every library with a static-libs USE flag will have a bunch of other |
| 11 |
libraries "copy & pasted" into it, and all of those copies take up |
| 12 |
their own separate chunk of RAM. |
| 13 |
|
| 14 |
Personally, I would disable static-libs. Within Gentoo the flag is |
| 15 |
mostly there because GNU autotools makes it easy to do -- not because |
| 16 |
it's a well-thought-out and reliable feature. But if it solves a more- |
| 17 |
annoying problem for you, then maybe it's worth it =) In that case |
| 18 |
lowering the -j flag for specific packages when you get an allocation |
| 19 |
failure is a reasonable workaround. |
Archives