Description of problem: The "-traditional" and "-traditional-cpp" switches cause an error with gcc32. Version-Release number of selected component (if applicable): $ rpm -q compat-gcc-32 compat-gcc-32-3.2.3-47.3 How reproducible: Every time Steps to Reproduce: $ echo "main(){}" > foo.c $ gcc32 -traditional-cpp foo.c Actual results: gcc32: installation problem, cannot exec `tradcpp0': No such file or directory Expected results: successful compilation, e.g., "gcc -traditional-cpp foo.c" Additional info: This is the same as bug 193144, except I still care that this bug is fixed. (I am unable to reopen that bug.)
Can you explain why you can't use gcc -traditional-cpp foo.c instead?
I wish to build libraries for the gcc 3.2/3.3 ABI.
The C ABI is the same.