|
|
|
|
|
|
by qiqitori
2951 days ago
|
|
|
> Now I have to put that work-around in my compilers. That seems really minor to me... Just because it takes a long time to find the root cause of a bug doesn't mean that the root cause was a stupid decision. Disclaimer: I partially work as a developer/support engineer for a RHEL-derived OS, but use Debian at home. |
|
|
They are relying on specific hacks in the GCC compilers' backends in order for their rpmbuild back-end tools not to bust. That's lack of insight and lack of architecture: what if I were using Sun Studio compilers for Linux, or intel compilers, or PGI compilers? rpmbuild will bust. They didn't think it through, and they never do. It's so stereotypical of them: for the past 20 years they've been haphazardly hacking, and never learned from their mistakes on how to actually engineer systems and how to architect solutions. Just take a look at the hacks they perform in their .src.rpm's, and it's crystal clear.
And "-Wl,--build-id" work-around I had to pull was just one example. I have many.