On Fri, Nov 21, 2008 at 03:57:15PM +0000, IainS wrote:
> hi,
>
> a freshly-checked-out gcc trunk, bootstraps fine and check is OK on gcc.
> However, I'm finding a huge number of failures with g++ caused by the
> fact that __Unwind_GetIPInfo is not defined.
>
> When 'make checking', I conventionally move the built libgcc_s.1.dylib
> and libgcc_s.10.4.dylib to one side prior to testing (so that the
> Apple-supplied system version is used).
>
> __Unwind_GetIPInfo is not present in the stock:
> /usr/lib/libgcc_s.1.dylib or /Developer/SDKs/MacOSX10.4u.sdk/usr/
> lib/libgcc_s.1.dylib
>
> [the symbol IS present in libgcc_s.1.dylib built from trunk]
>
> ---
> Is this the expected behavior? (there doesn't appear to be an update to
> the library version).
>
> If so - I guess that anyone building with 4.4 would have to supply an
> updated libgcc ???
>
> cheers,
> Iain
>
Iain,
Since the libgcc can contain new symbols which older libgcc's may not
and libstdc++ is built against this newer libgcc, I wouldn't expect it to
necessarily work. I would note that the recommended approach for building
llvm-gcc42 is for the FSF gcc's libstdc++-v3 to be removed from the source
tree so that the system copy is used. I wouldn't be surprised if the
stock gcc-4.2 compiler in Xcode 3.1.x was doing the same (building against
the legacy libstdc++ from gcc 4.0.1). On fink, we always package the libgcc
from the FSF gcc releae in question and link against that by default.
Jack
