[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: how to find symbols needed for libgcc-compat in glibc



Guido,
    The problem is running binaries built under gcc < 3.1 with this
glibc. If you have installed the glibc 2.3 that you built with gcc 3.2,
check if those binaries with the undefined symbols...

__divdi3
__ucmpdi2
__udivdi3
__umoddi3


still run. I suspect they will not. A sysdeps/mips/libgccc-compat.c
will have to be created for mips which provides these symbols for run-time
resolution but not exported for linking. 
                       Jack



Reply to: