Elektrine lite

← Feed

@pinskia@hachyderm.io

Post #2272210

2026-04-28 16:53 UTC

@bshn@hachyderm.io Gcc compile is not bad if you just compile gcc and not the target libraries and not do a bootstrap. Maybe 5-10 minutes. Incremental builds are really fast; I do them all the time. Just dont touch a shared header otherwise everything gets rebuilt. Where gcc build gets slow is more about the target libraries and multilib (which you can disable) and the bootstrap. Doing the bootstrap is you build most of the code 3 times including the runtime libraries. `${src}/configure --disable-bootstrap --enable-languages=c++` is the fastest. When doing gcc development I mainly take a previous built objdir and the update the sources and just rebuild cc1/cc1plus and run a small subset of the testsuite. When I am happy with the patch i run the a full bootstrap/test cycle (takes 2-3 hours now). Testsuite takes a long time these days. Most folks wont run the testsuite so ....

Replies (1)

  • @bshn@hachyderm.io 2026-04-28 17:34

    @pinskia@hachyderm.io thanks Andrea. I just was fascinated that my PC frooze when I started to build it without restrictions. -j4 and —nocheck speed it up significantly

    Open ##2272211