Debugger versions mess

Rebuild gdb from source would appear to be a trivial solution. Presumably you already have a way to compile for the target. Just build a new gdbserver for it.

Cheers,

Thanks,

That's what I would like to do, but the embedded computer is so small that there is no compiler on it. In fact I think this is a more general problem as my own application is likely to have the same problem as the gdbserver with libc. I have so far just been trying the debugger with the application compiled on the old RH.

So I guess my question is more general like: How do I get the gcc to link with an older libc and not just the current in the lib directory?

I would have to do that for both the gdbserver intended for the embedded and for my own application. Am I right?

Jens.

If you kept a copy of your older RH filesystem around you could chroot into it, and do your compilations from there. Or reinstall a small version of it to use as a chroot environment.

While it is probably possible to link to an older version of libc under your new system(this is a guess), it would probably require all sorts of odd command line options or wacky gcc modifications. Probably a royal pain if you are trying to compile stuff with overly complicated build scripts(like automake/autoconfig).

Karl.

Jens wrote: