>
>
> The changes I made related to versioning went into glibc (2.2) on
> 2000-03-30 or thereabouts and into hurd/libthreads at about the same time.
> It is not too surprising to have a problem with an old glibc and a new
> hurd. I am not able to do any real hacking or even much code-reading these
> days (it will be probably at least several more weeks before I can), and I
> don't recall the full details of all this off hand. I don't think there
> should be a problem like this, but I don't have enough information on hand
> right now to be of much more help. Mark understands the details too and
> might be able to help before I can.
>
> If those of you who have a problem and those who don't can compare details
> of what you are doing more closely, then that may help us figure it out.
> Collect clear and exact information about what code everybody is using, and
> output of objdump --private-headers and objdump --syms and see how they
> differ. (Those two objdump output modes together tell you basically
> everything about the symbol versions.)
Hi
I may be able to run this with gdb this week. Had to reload the tar ball before
anything worked; but the situation is confused as this machine is faulty and
needs a new mother board and processor. This may have to wait until I relocate,
the farm's auction is in 10 days.
OK. Have gcc-2.95.2. Recent Hurd source that will crash; and libc0.2-dbg
2.1.3-6 (native built with gcc-2.95.2.)
Am thinking of running a sub-Hurd, after replacing hurd/ext2fs.static and
lib/libdiskfs.so
Chris
