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

Re: Status update hppa - glibc 2.2.92 (Problems with __divdi3)



Carlos,
    I think you are looking in the wrong place. The libgcc symbols
in question, that were improperly exported from libgcc, were made
.hidden at gcc 3.1 and later. So if you were exporting libgcc symbols,
the binaries built with gcc 3.0 would definitely be impacted when these
symbols disappear (when glibc is rebuilt with gcc 3.2). Unfortunately the
way you have to test for these symbols is rather ugly and both Jakub
and Franz has thrown out the scripts they wrote for ia64 and ppc to do
this. You have to make list of all the symbols in libgcc from gcc 3.0
and then search all the binaries installed on your machine for
undefined instances of these symbols. If you see one, then libgcc
was incorrectly exporting that symbol and it will have to go into
a sysdeps/hppa/libgcc-compat.c to be presented there for run-time
resolution (but not linking). Sorry that it isn't easier to do.
    Of course if you have a rescue disk available to fix you machine
from, you could try the brute force approach. Rebuild glibc 2.2.5
with gcc 3.2 and install that glibc. If nothing breaks you may
not have an issue. However you will have to look carefully at things
like sendmail, etc to see if anything fails to run because of
the .hidden libgcc symbols in gcc 3.2.
                      Jack



Reply to: