On Wed, 9 Mar 2005 19:57:00 +0000 (UTC), Jason Lunz <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] said: > > I just figured out a way to do this for the ssh binary. Maybe this would > work for you? > > Here's what I did: > > $ apt-get source ssh > $ cd openssh-3.8.1p1 > $ debian/rules build
I appreciate the thought, but actually building glibc (and the nptl add-on) is a dangerous and daunting task. I looked into it for about half an hour, but glibc is a different order of beast from ssh entirely: it requires considerable configuration which is not for the casual developer, and installing it is a *very* touchy business. Of course, I would really only need to install the libpthread.a archive, but even so, building the whole glibc package is an involved and intensive undertaking and moreover... > Is there anything wrong with doing this? I have by doubts that this is > completely foolproof. Any libc macros or inlines will come from the > build system's libc, for example. I don't know if that can cause > problems when a different glibc version is dynamically linked at > runtime. Exactly. So I decided against this course of action entirely. For just about any application or library *other* than glibc, this would be the right approach for my needs. -Blunt -:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
