There's at least two hack-a-rounds for gcc fubar'age in rpm.
The documented hack is in lib/verify.c:
/*
* XXX Sick hackery to work around qva being clobbered on CentOS3
* XXX using gcc-3.2.3-49.x86_64.
*/
There's another pukiness on s390 w stat(2) that I can probably find
with some vermouth.
Keep the hacks or not?
Personally, I'm tired of fixing problems in rpm like this. If your
compiler is broke,
rpm is not the only piece of code that is gonna break, and rpm is
certainly not the
right place to fix compiler problems.
What say ye?
73 de Jeff
______________________________________________________________________
RPM Package Manager http://rpm5.org
Developer Communication List [email protected]
