Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Tue 30 Sep 2014, 06:07
All times are UTC - 4
 Forum index » Off-Topic Area » Programming
How to install new libc-2.7.so file in Puppy400 ?
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [4 Posts]  
Author Message
sunburnt


Joined: 08 Jun 2005
Posts: 5032
Location: Arizona, U.S.A.

PostPosted: Thu 22 Oct 2009, 18:57    Post subject:  How to install new libc-2.7.so file in Puppy400 ?  

Not quite programming, but... I have an app. that needs libc-2.7.so
Puppy400 has libc-2.6.1.so, I got one from the Debian stable release.
Do I just drop it in /lib and make a new link: libc.so.6 => libc-2.7.so and then reboot???
I`ve done libraries before, but just for apps, this one`s critical!
Back to top
View user's profile Send private message 
caleb72

Joined: 15 May 2009
Posts: 57

PostPosted: Thu 22 Oct 2009, 22:04    Post subject:  

I don't necessarily know where new libraries go specifically. However, what I usually do when I need to download a new library (usually from Debian), I either click on the .deb package and allow it to install itself (Puppy 4.3) or I use the deb2pet utility to convert it to a .pet and then install it automatically (< Puppy 4.3).

Does this help at all?

Regards
Caleb
Back to top
View user's profile Send private message 
amigo

Joined: 02 Apr 2007
Posts: 2251

PostPosted: Fri 23 Oct 2009, 07:13    Post subject:  

"just drop it in /lib" and break your system! You can't go replacing your glibc stuff without breaking lots of stuff or re-compiling it all.

But, you can still make it work by doing this:
1. place the libc.so file in some out-of-the-way-place, say:
/usr/local/glibc-7
Then create a wrapper for the program you want to run, say it is called 'my-proggie'. Rename that to 'my-proggie-bin' and place in your normal path )/usr/bin or other such).
the create an empty file called 'my-proggie' and put this in it:

Code:
#!/bin/sh

export LD_LIBRARY_PATH=/usr/local/glibc-7
exec my-proggie-bin

Back to top
View user's profile Send private message 
mikeb


Joined: 23 Nov 2006
Posts: 8257

PostPosted: Fri 23 Oct 2009, 08:09    Post subject:  

ok...you would first need the full set of libraries and not just the one lib including locales and such.
Using an installer usually fails as the order is critical...one wrong move and seizure.
I have done this live.......added the libs manually first...painless.
Then deleteted and remade (or copy from fileset) each symlink in turn doing libc last....literally starting from the bottom and working upwards using rox.

Otherwise add to the pup_save.2fs when not in use or a full install to the file system not live.

If all goes well then remove the old libs otherwise if a frugal mount the pup_save and clear out the added files.

I have changed puppy 2.02 and 2.12 to glibc 2.3.6 TLS and now 2.6.1 sucessfully so me not making this up Very Happy

mike
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 1 [4 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Off-Topic Area » Programming
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0447s ][ Queries: 12 (0.0043s) ][ GZIP on ]