News for hackers. Stuff that matters.
Re:The C++ Build Process Explained by colanderman on Wednesday November 14, 2018 @08:41PM (#18456172)
> Now check if any symbols are missing again and repeat until done.

That properly describes linking using --start-group/--end-group. Without those flags, the process is closer to "look in the first .a file for definitions of all currently undefined symbols; then look in the next .a file for definitions of remaining undefined symbols; etc.". The difference becomes apparent if you link chains of libraries in the wrong order, or if you have cyclic dependencies between libraries; normally they will not be resolved unless you use the grouping flags. (But really, you should avoid making such cycles in the first place!)

Re:The C++ Build Process Explained by aidenn0 on Thursday November 15, 2018 @12:09PM (#18461064)
Thanks for the correction. I was posting that from my phone without any references in front of me.
Re:The C++ Build Process Explained by jacobush on Thursday November 15, 2018 @03:12AM (#18457682)
This is the first explanation I have understood of this perplexing phenomenon.