From: Robert Hoehne <Robert DOT Hoehne AT Mathematik DOT tu-chemnitz DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Shared libraries
Date: Wed, 28 May 1997 12:48:57 +0200
Organization: TU Chemnitz-Zwickau
Message-ID: <338C0D99.77C66D4C@Mathematik.tu-chemnitz.de>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 970527101740 DOT 10847K-100000 AT is>
NNTP-Posting-Host: pandora.hrz.tu-chemnitz.de
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 23
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Eli Zaretskii wrote:
> 
> There is a trade-off here between polluting the disk and reliable
> operation (what would be your first reaction when a just-unzipped
> program won't run saying something like "couldn't file djgpp.dll:
> ENOENT"?), and most people prefer the latter, especially since disk
> storage is so cheap these days.

In addition to this I have an other example. When I made my first
linux version of RHIDE I linked it using the shared libraries. Then
I took it here at university and tried it on our PPro 200 and I got
a segfault. But the same program linked static worked OK.

As you can see, using shared libs is not always the best solution.

Robert
-- 
*****************************************************************
* Robert Hoehne, Fakultaet fuer Mathematik, TU-Chemnitz-Zwickau *
* Post:    Am Berg 3, D-09573 Dittmannsdorf                     *
* e-Mail:  Robert DOT Hoehne AT Mathematik DOT TU-Chemnitz DOT DE              *
* WWW:     http://www.tu-chemnitz.de/~rho                       *
*****************************************************************