[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Errors in compiling a source package



> Now there's a rather strong warning against downgrading ldso to version
> 1.8.x, which is the option I'm looking at here, since I can't install
> libc6 without gutting my system, making it near impossible to do what I
> wanted to do in the first place, that is to compile a source package.  

Well, I more-or-less understand why you wanted to upgrade ld.so, and
why the upgrade didn't do what you wanted to. But I still fail to
see why you want to downgrade ld.so. Really the hamm ld.so doesn't
conflict/depend on anything in bo/hamm, so you should be able to
use the hamm ld.so safely on a bo system. Really, unless you have
_very_ good reasons to downgrade your ld.so, *don't* do it!


> Why is this warning there?  

Well, I'm tempted to say "just try it, punk". But I won't, as that will make
your system completely unusable: every command (cp, ln, bash, *everything*)
will stop to work.

> Is there anything I can do manually to downgrade my machine's ldso?

There should be: (untested!):

  cd /tmp
  mkdir ldso
  dpkg --extract /tmp/ld.so.-bo-version-.deb ldso
  cp -a ldso/lib/* /lib
  
  dpkg -i /tmp/ld.-bo-version-.deb


But I advice against this. And, it's so untested I would hesitate
to use it on my computer.

(Ah, well, I was one of the first to fall for the ld.so downgrade trap,
and, after that I was so shocked at the results that I put statically
linked versions of cp and friends in /static/bin. With those files
I'd be able to get my system back on it's feet. But if you don't have
them, well, you'll have to hard-reset your system, and boot from floppy).

Wish you luck!
-- 
joost witteveen, joostje@debian.org

Potentially offensive files, part 5: /dev/random: 
`head -c 4 /dev/random` may print 4-letter words (once every approx 4e8 tries).


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .


Reply to: