On Mon, 27 Sep 1999, Tim Hillman wrote:
> None of my existing binaries work. They all complain of the same
> undefined symbol (It escapes me at the moment, but I will re-create it and
> get the exact name if I didn't go about this the wrong way).
Would it be something along the lines of "__register_frame_info"? If so,
the problem is related to the c compiler. If you compile glibc with egcs
1.1.2, that problem will probably go away. OTOH, if you ask nicely on the
[EMAIL PROTECTED] you may be able to get a patch for this. IIRC, it's not a
bug, it's a feature.
> Is 2.0.7 binary compatible with 2.1.2 ?
The answer is yes and no. AFAICT most problems are to do with developers
using internal glibc symbols[1]. You might find it worthwhile to use the
glibc-compat addon, though.
[1] I'm a little hazy on this, but WTH.
--
Understanding is a three edged sword. Do you *want* to get the point?
http://www.albatross.co.nz/~psycho/ O-
