Re: packaging static lib oriented software
"James A.Treacy" <treacy@debian.org> writes:
> Scott K. Ellis wrote:
> > You've missed the fact that Linux uses demand-paged code. If a specific
> > page of a library isn't used, it isn't loaded into memory (or is at least
> > easily discarded).
>
> This may be, but the picture doesn't seem to be that simple. There
> are stories that sites have had trouble with a number of people
> running the same program when linked against a shared lib. The same
> site had no problems when they switched to running a statically
> linked version of the program.
>
> That's a little short on details and long on heresay, but I
> have no reason to doubt the story.
One scenario where such a thing could happen: the object files composing
the `.so' file weren't compiled with -fPIC. `gcc' creates "shared"
libraries from non-PIC files too, but non-PIC shared libs aren't shared
among processes.
- Hari
--
Raja R Harinath ------------------------------ harinath@cs.umn.edu
"When all else fails, read the instructions." -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing." -- Roy L Ash
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: