Path: news.cs.au.dk!not-for-mail From: Arne Hueggenberg Newsgroups: comp.lang.beta Subject: Re: Problems with Slackware 2.0.36 Date: 19 Apr 1999 10:07:54 -0000 Organization: University of Dortmund, Germany Lines: 32 Approved: mailtonews@cs.au.dk Distribution: world Message-ID: <19990419100754.18847.qmail@noatun.mjolner.dk> Reply-To: Arne Hueggenberg NNTP-Posting-Host: daimi.cs.au.dk X-Trace: xinwen.cs.au.dk 924516589 1407582 255.255.255.255 (19 Apr 1999 10:09:49 GMT) X-Complaints-To: news@cs.au.dk NNTP-Posting-Date: 19 Apr 1999 10:09:49 GMT Xref: news.cs.au.dk comp.lang.beta:11900 On Fri, 16 Apr 1999 , Daniel Sawitzki wrote: > Hello > I've developed a beta-program called movie-keeepr > (http://studserver.uni-dortmund.de/~su0754/mk/mk.html). A user wrote me= , > that it doesn't started on his Slackware 2.0.36 Linux distribution. The > Linux binary i released was copiled on a SuSe 6.0 Linux (glibc2-baed). = I > have linked it statically with Lesstif. Because this static linking i > thought it's not important what kind ob libc the user has installed. Am > I wrong iwith this conclusion? I would say so. AFAIK binaries linked against glibc2 wont run on libc5 systems and vice v= ersa (unless of course the other libs are provided for compat reasons). I guess that the Slackware he is using is quite dated and thus wont have = glibc2 support (unlike for example suse 5.3 has) Now, as many Distros still have the libc5 provided for compability reason= , might it be possible to manipulate BETALINKOPTIONS in such a way, as to e= nforce linking against the libc5 libs wich are lying around somewhere? > Thanks > Daniel Sawitzki Arne Hueggenberg