Puppy Linux Discussion Forum

[sc0ttman]

I would like to run some stuff that was compiled in Lupu/Lucid or whatever uses libc 2.11

I'm using a wary based Puppy, which is on libc 2.10, so the command:

[big_bass]

Hey sc0ttman

[Dave_G]

Hey sc0ttman,

Go for it, nothing wrong with firing up the ol' hex editor.
One of two things are going to happen:

1) The app expects a function or variable type in the "new" lib which is not in the old one which you just renamed and will crash, oh well at least
you will know.

2) It will work.
Sometimes the dev just cleans up the code and ups the version number
but the lib is functionally the same as the older one.

Oh and by the way, in case you haven't done this kind of thing before,
when hex editing an executable keep the new strings the same length
as the old ones or you will trash the whole thing.

Dave.

[technosaurus]

I used to have an object file that I could preload with ldpreload that had stubs of these pseudo functions. I usually just make it a void function or if it needs to be an int function, just return 0. It was handy to have around for just these sorts of things without having to track down and compile a bunch of packages.

[sc0ttman]

Thanks for the replies guys, bigbass - I know its a dumb thing to do, but thats just me...

I've been 'off my face' on various medications the past 3 days, literally not knowing if yesterday morning was today or not, where I was 5 hours ago, and so on... But then the GLIBC hacking idea came to me, so I thought I would ask!

Dave G, I was thinking today as well... I cannot replace anything with GLIBC_2.11, except GLIBC_2.10, which is the real one, so that would probably break everything...

And Techno, I wish that info wasn't SO far above my head (I'm on lots of pills for a bad neck in the 1st place lol)..

But anyway, thanks for the replies, I thought I would ask - and was basically waiting for amigo to come and tell me to stop being an idiot.

[big_bass]

[amigo]

Did I hear my name?? The best way to do what you want is to install the needed library in an out-of-the-way location. Then, use a script wrapper to set LD_LIBRARY_PATH to point to the library before exec-ing the binary which needs that library. This avoids borking your system by arbitrarily replacing glibc. You need to understand that nearly everything on your system uses glibc, so replacing it without recompiling everything against the new version is very risky. Many programs will continue to work normally, but there will nearly always be some which do not -often in subtle ways which may not be immediately obvious. You can always use the new version for other programs as well -just use a wrapper for each program you want to use that version.

Sorry to hear about your neck -if you are taking NSAID's like ibuprofen, etc, try to find a way to not take them for long as they will ruin your kidneys. I've just found out the hard way by having a kidney fail (leading to super-high blood pressure). One of the better ways to deal with the neck pains is by taking tricyclic anti-depressants -particularly nortryptilin. I have 6 bad disks in my neck, chest and lumbar regions and a seventh already removed, so I have a *little* experience with the subject...

[Dave_G]

amigo wrote:

[technosaurus]

if the working library was in /usr/share/myapp

[Dave_G]

Thanks technosaurus

[sc0ttman]

[Makoto]

Okay, now you've got my attention as well. I've been way too paranoid to attempt mucking with the versions of glib/c in my setup... which sc0ttman knows.

sc0ttman: Hope you're feeling better, for whatever reason you were taking the medications.

[sc0ttman]

[Makoto]

Yes, but I meant the more technical doctor's explanation, though (not that I'm asking you to mention what it was). You did say it was serious enough that you had to take various medications.