I am curious about whether LSB will (or should) take up the question of the
__register_frame_info symbol (and friends) that egcs puts into some of the
glibc-2.0 shared libraries.  

(Briefly, egcs-compiled executables linked against these libraries expect
this symbol to be defined in the runtime environment, so these executables
can't be run on systems with gcc-compiled glibc-2.0.  There is a nice
description on the answer to FAQ#2.8 in the glibc-2.1.0 distribution.)

        -Paul Kimoto <[EMAIL PROTECTED]>

Reply via email to