29 Mar
2006
29 Mar
'06
17:33
* Steve Graegert (graegerts@gmail.com) [20060328 09:06]:
due to a patch that has been incorporated by the vendor.
OK, but I wouldn't have call that "wrongly patched" but rather something like "bug in $VENDOR version of gcc".
Since you obviously have more details about the issue than we do,
Knowing the tools you need to check something like this helps, in this case nm and objdump. nm with either --defined-only or --undefined-only (plus possibly --demangle in both cases when dealing with C++ code) quickly shows symbols present or missing. Non-standard compiler flags like -fno-unit-at-a-time should always be the prime suspects and that's what I tested first. Philipp