Re: installing glibc 2.1.x and 2.2.x in parallel?
On Fri, Jul 06, 2001 at 08:53:46PM -0400, Jimmy Kaplowitz wrote:
> Warning; the below post might be better on -user, or -powerpc, except that I
> have cleverly managed to erect a thin veil of relevance that ties it in to the
> question I am replying to. I posted a post about this saga on -powerpc
> yesterday, but have gotten no responses, whereas I have tried very hard today
> to get the installation working, yielding the problems described below.
>
> On Fri, Jul 06, 2001 at 10:39:09AM -0700, Daniel Jacobowitz wrote:
> > Use LD_LIBRARY_PATH, and instead of running ./executable, run
> > /foo/lib/ld-2.1.3.so ./executable. I hope you don't want that program
> > to exec() anything else, though.
>
> What do you do if the program may exec something else? I may be having
Don't let that happen! Running an older glibc is never, ever
supported.
> problems related to this in attempts to install Debian on a rather resistant
> G4. For example, assume I'm running off of a CD-ROM burned from a CVS build
> of boot-floppies from 30 Jun 2001. This uses busybox and an old libc. I want
> to chroot into my mounted filesystem and open up a shell and have the ability
> to install packages, compile kernels, etc. -- in other words, do everything --
> without some packages giving me segfaults, illegal instruction errors (sig 4),
> shared library errors, and obscure errors I've never seen before having to do
> with something called Verneed sections. (All of this actually happened. It's
That's VERNEED, I assume.
I have no idea what you're doing but it sounds to me like you have a
hardware problem. chroot is the proper way to use the target
filesystem; errors after chroot have nothing to do with the ld.so on
the outside.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
Reply to: