Thomas.
   From having built a number of apps from scratch for work myself I've found one thing that really is a bust when it comes to doing the static build. glibc If your app was designed with the same glibc that you have you can often get around the problem. Most configure programs offer the option to build static. Then you are ususally good to go. Another way around it is to create a directory called (for example) /usr/local/mylibs. Manually put the libs need by an app in this directory then add /usr/local/mylibs to the END of the ld.so.conf file ( that way it's the last place an app looks and shouldn't screw up anything on your box.) The the updated libs are isolated from your systems libs but available to apps that ask for them instead of the system libs. (be sure and run ldconfig) WARNING I've done this a number of times and so far I've only lunched a box once (glibc libs don't work with this method for example) So please for your sake test it on a non production box be!
fore you go live. If you do screw up a box. Boot from a rescue disk (I've found the slackware linux on a disk or the mandrake linux on a disk to be real helpful if you don't have a normal rescue disk) remove the offending lib(s) and reboot. The box will return to normal. Hope this helps.

James
 

On Sat, 19 Jan 2002 10:07:08 -0000
"Thomas Mangin, Home" <thomas.manginfree.fr> wrote:

> |or whatever version you are running. (BTW, I run ssh on this box
> |instead of openssh because openssh requires lots of library upgrades
> |that I won't do on this old RH box).
>
> I must say that it is a real problem to upgrade SSH, and sometimes some
> other application on old server with high load.
>
> It is not SSH specific but SSH beeing on all server, it HAVE TO be upgraded
> as often thrid parties need access to the computer and you can not simply
> firewall the application.
>
> What about an option in the SRPM to recompile them staticly ?
>
> It should avoid the dependancies and simplify the upgrade of old boxes.
>
> Thomas
>
>
>
>
> For help, email discuss-helpmandrakesecure.net; to unsubscribe send a
> message to discuss-unsubscribemandrakesecure.net. To visit MandrakeSecure,
> go to http://www.mandrakesecure.net/.
>
>

For help, email discuss-helpmandrakesecure.net; to unsubscribe send a
message to discuss-unsubscribemandrakesecure.net. To visit MandrakeSecure,
go to http://www.mandrakesecure.net/.

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]