Albert Chin wrote:
I set ':set showmatch' in vim and all the braces match up.
Yes, the braces match up. You wouldn't have been able to build gcc if they didn't.
However, they are still wrong. One of the braces is in the wrong place, and has to be moved. It looks like someone tried to modify the libgcc specs, got a build error, then added a brace to fix it, but mistakenly added the brace in the wrong place.
As mentioned before, there is a brace missing after the gcc_s_hpux64. This brace is needed to close off the shared-libgcc rule before the static-libgcc rule starts. You then must delete a brace from the end of the !static rule which has one too many.
The libgcc spec in the FSF gcc sources do not match the one you have given, so this appears to be a bug in patches that you or HP have added to gcc.
Alternatively, it could be a miscompilation problem, but that seems rather unlikely.
The above is from gcc-3.4.3 + some patches. However, the HP 3.4.4 binary has the same "*libgcc" line. Do you have a GCC 3.4.x binary on HP/IA-64 which works correctly with -shared?
I do not have an ia64-hpux machine. I have an HP loaner, but not a copy of HPUX, so my machine is only running linux.
-- Jim Wilson, GNU Tools Support, http://www.specifix.com
