[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Nonstandard lib location & LD_RUN_PATH
From: |
David Masterson |
Subject: |
RE: Nonstandard lib location & LD_RUN_PATH |
Date: |
Tue, 29 Nov 2005 12:23:26 -0800 |
Martin, Jason H wrote:
> -static would work. The downside is that a totally static-linked
> binary is very large. The effect is multiplied when you consider that
> cfservd / cfrun / cfagent all would have their own statically linked
> copy of libc/openssl/berkeleydb. I am aiming to avoid that as disk
> space is an issue on some hosts.
Hmmm. It's also an issue with respect to upgrades of libraries...
--
David Masterson
VMware, Inc.
Palo Alto, CA
- Re: Nonstandard lib location & LD_RUN_PATH, (continued)
RE: Nonstandard lib location & LD_RUN_PATH, Martin, Jason H, 2005/11/29
RE: Nonstandard lib location & LD_RUN_PATH, David Masterson, 2005/11/29
RE: Nonstandard lib location & LD_RUN_PATH, Martin, Jason H, 2005/11/29
RE: Nonstandard lib location & LD_RUN_PATH, David Masterson, 2005/11/29
RE: Nonstandard lib location & LD_RUN_PATH,
David Masterson <=