Red Hat says GCC 2.96 doesn have bugs anymore [www.redhat.com]. Why don you allow it to be used with Services?
Because, as Red Hat themselves admit (and just about anyone involved in Linux development can tell you), some releases of GCC 2.96 did have serious bugs in them, and I have personally verified that at least some releases of 2.96 fail to compile Services correctly. Since Red Hat, in one of their many stupid decisions, chose not to change the version string in the fixed releases, I have no way to tell whether a given release of GCC 2.96 is a “fixed” one or not. Rather than have to wade through assembly listings for every case of a bad GCC release, I’ve chosen to disallow the use of GCC 2.96 entirely. The previous version of GCC, 2.95.3, is known to work correctly with Services, as are more recent versions (3.2 in particular); either downgrade or upgrade before compiling Services, or install from a binary distribution instead of the source code. If you absolutely must compile Services using GCC 2.96, you can override the configure check with the -force-gcc-2.96 option. However, the author
Related Questions
- Foxit Reader for Desktop Linux used GCC version: 4.3.0 20080428(Red Hat 4.3.0-8) 5. Will you add any more features in Foxit Reader for Desktop Linux, in the future?
- Red Hat says GCC 2.96 doesn have bugs anymore [www.redhat.com]. Why don you allow it to be used with Services?
- Which versions of browser should be used to access the i-Securities Services system?
