Hello All!

gcc is a problem for me to compile on my very small vps with just 1GB ram

gentoo devs tell its no problem, hmm

how does other solve it ?

i know it works with 4GB


Regards Benny

... too late to die young :)

--- Msged/LNX 6.1.2 (Linux/7.2.12-gentoo-dist-bin (x86_64))
* Origin: gopher://fido.junc.eu/ (2:230/0)

Hey Benny!

On Sun, Oct 25 2026 13:37:34 +0000, you wrote:

gcc is a problem for me to compile on my very small vps with just 1GB ram gentoo devs tell its no problem, hmm
how does other solve it ?

With Gentoo itself, "MAKEOPTS=-j1" should help with that, with a minimum 2gb swap.

Otherwise, if you're using gnu make.. `make -j1` will do the same:

-j [jobs], --jobs[=jobs]
Specifies the number of jobs (commands) to run
simultaneously. If there is more than one -j option, the
last one is effective. If the -j option is given without an
argument, make will not limit the number of jobs that can run
simultaneously.

With less memory and/or cpus/threads, you can't compile multiple jobs at once. Even with that said, larger packages might still fail this way.

Depending on how many cores/threads that VPS has, you can adjust the "-jX" option accordingly (2 cores/threads = "-j2" would be max, 1 core/thread = "-j1", etc.).

It seems the /suggested/ method is to compile small packages on the VPS, and use binary packages built on a stronger machine for larger ones. Or just use Gentoo's binary package manager right on the VPS.

Regards,
Nick

... Politicians and diapers should be changed regularly for the same reasons. --- AmberEdit/linux 0.9.3
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Hey Benny!

gcc is a problem for me to compile on my very small vps with just
1GB ram

Add swap. 4G ought to do it.

Life is good,
Maurice

-o -o -o o- o- -o -o o- o- o- o- -o
(\ (\ (\ /) /) (\ (\ /) /) /) /) (\
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
... Æfter leofan menn langað swiðost.
People long most for a loved one.
--- GNU bash, version 5.3.20(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

Hello Nick!

Sunday October 25 2026 13:32, you wrote to Benny Pedersen:

With Gentoo itself, "MAKEOPTS=-j1" should help with that, with a
minimum 2gb swap.

I did not use Gentoo long time, but I remember if job number is not set,
then the build system will use number of logical processors. So, on
small VPS with one core, it will be "-j1" anyway.

I'm not sure 2GB of swap will be enough on a 64-bit system. Probably 4GB
and more.

It seems the /suggested/ method is to compile small packages on the
VPS, and use binary packages built on a stronger machine for larger
ones. Or just use Gentoo's binary package manager right on the VPS.

Sad, but true. That is modern life. Looking forward and scary about what
will happen with all these vibe-coded-neurogenerated fancy Rust code in Kernel...

I used to write drivers for Linux Kernel since 2002, and saw all its
path from clean structure to enterprise-grade-overengineered piece of
art.


With best regards, Sergey.

... I must not fear. Fear is the mind-killer.
--- GoldED+/LNX 2.0.0-b20260912
* Origin: Submarine Pilot, Bandhagen, Sweden (2:201/127)

Hey Sergey!

On Sun, Oct 25 2026 19:50:38 +0100, you wrote:

With Gentoo itself, "MAKEOPTS=-j1" should help with that, with a minimum
2gb swap.

I did not use Gentoo long time, but I remember if job number is not set, then the build system will use number of logical processors. So, on small VPS with one core, it will be "-j1" anyway.

I also have not used Gentoo in a very long time. Thanks for the information!

I recently ran into kind of the same issue on one of my VMs with 2 cores and 4gb ram, using "cmake" with no options and it failed. I ended up fixing the issue with the "-j2" option. I had thought "cmake" would use the number of logical processors as well, but for some reason it didn't.

I'm not sure 2GB of swap will be enough on a 64-bit system. Probably 4GB and more.

You are definitely right. I originally had "minimum 2-4gb", but saw such a small amount of allocated ram so I changed it, hoping he wasn't trying to install firefox or chromium or something ridiculous like that.

Sad, but true. That is modern life. Looking forward and scary about what will happen with all these vibe-coded-neurogenerated fancy Rust code in Kernel...

We've already witnessed the dumbing down of the population with social media, keeping people glued to their phone for hours on end. It's only going to get worse, I fear.

I used to write drivers for Linux Kernel since 2002, and saw all its path from clean structure to enterprise-grade-overengineered piece of art.

I'm willing to bet you replaced whatever you were originally thinking with "art". ;)

Regards,
Nick

... If at first you don't succeed, destroy all evidence that you tried.
--- AmberEdit/linux 0.9.3
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Hello Nick!

Sunday October 25 2026 14:24, you wrote to me:

I recently ran into kind of the same issue on one of my VMs with 2
cores and 4gb ram, using "cmake" with no options and it failed. I
ended up fixing the issue with the "-j2" option. I had thought "cmake" would use the number of logical processors as well, but for some
reason it didn't.

For cmake there are --parallel option and CMAKE_BUILD_PARALLEL_LEVEL environment variable. If no one CMakeLists.txt in the project or included scripts are overriding this option, and option is not set, then cmake will
use settings from native build system (make, ninja, and etc).
Maybe something was overriden by build script (via environment) at the upper level. Or on some lower level as well, in subdirectory project files. Or the native build system had specific configuration with overrided parameters. Recently I saw similar problem in Yocto Linux. The bitbake selected 10 parallel jobs by default, for some unknown reason, while host is 4-kernel CPU with 8 logical processors.


With best regards, Sergey.

... I must not fear. Fear is the mind-killer.
--- GoldED+/LNX 2.0.0-b20260912
* Origin: Submarine Pilot, Bandhagen, Sweden (2:201/127)