PC for Compiling

[Lunar_Mare]

Hello guy,

This my first post. i hope this received by this community.

 

TL;DR

Did you had recommendation about compile farm PC setup ?

 

Recently, i see many people giving impression about building gaming rigs ,

3-D graphic render rigs and etc. But there are rare impression about PC build

focused for compiling and linking program, in sort building program rigs.

 

How this idea come to my mind ? I see many GNU/Linux distribution come in

binary from, which is compiled first. there a tons of binary packages, exception

for Gentoo since that build in your own machine.so the question is, What kind

of PC setup handle that compilation progress? could i build it. 

 

Thank you.

 

P.S : I had recently meet after my littler research, few Youtube video talk about this.

they use AMD TR 2990 but without any further explanation about that.

 

P.S : Sorry for horrible English.

Edited July 11, 2019 by Lunar_Mare
Typos and adding some tags

[Mira Yurizaki]

Whether or not you need something like this depends on how big your project is and how fast you want it compiled.

[APasz]

By definition any computer is a "program rig". As to what can compile a program faster, that depends on your compiler.

From my experience (which isn't all that much), more cores of decent speed with plenty of ram is preferred.

[Lunar_Mare]

 

7 hours ago, APasz said:

By definition any computer is a "program rig". As to what can compile a program faster, that depends on your compiler.

From my experience (which isn't all that much), more cores of decent speed with plenty of ram is preferred.

I use GCC to compile operating system stuff like kernel , tools , etc. I use my old laptop to do that , i found something unique. if i do multitask , like i use my laptop to watch movie and compiling. the compiling progress get fail to segmentation fault, this which my program on compiling too.

[brob]

A segmentation fault suggests a software bug. A process is trying to read or write a piece of memory without permission. The root cause is often something like an out of bounds array reference or an invalid pointer reference.

 

Most compilation jobs have to be single threaded. Make can often be multithreaded. High core count cpu are not necessarily best, but four or more cores would be good. 

 

Storage speed is very important as many files are read and written during a compile or make.