Path: news.cs.au.dk!not-for-mail
From: "Sascha Kimmel" <kimmel@tricos.com>
Newsgroups: comp.lang.beta
Subject: AW: Problems with Slackware 2.0.36
Date: 19 Apr 1999 10:08:07 -0000
Organization: University of Aarhus, Department of Computer Science (DAIMI)
Lines: 53
Approved: mailtonews@cs.au.dk
Distribution: world
Message-ID: <19990419100807.18903.qmail@noatun.mjolner.dk>
Reply-To: "Sascha Kimmel" <kimmel@tricos.com>
NNTP-Posting-Host: daimi.cs.au.dk
X-Trace: xinwen.cs.au.dk 924516669 1404074 255.255.255.255 (19 Apr 1999 10:11:09 GMT)
X-Complaints-To: news@cs.au.dk
NNTP-Posting-Date: 19 Apr 1999 10:11:09 GMT
Xref: news.cs.au.dk comp.lang.beta:11901

Hi!

Slackware 3.6 contains runtime support for glibc2-based binaries.
Slackware 3.6 has the 2.0.36 kernel, so it might be that this should not
be the problem (well, if the runtime support *was* installed).
More info @ http://www.slackware.com

Regards,
Sascha Kimmel

> -----Ursprüngliche Nachricht-----
> Von: Arne Hueggenberg [mailto:zalaster@nef.wh.uni-dortmund.de]
> Gesendet am: Freitag, 16. April 1999 19:23
> An: Daniel Sawitzki; Daniel Sawitzki; usergroup@mjolner.dk
> Betreff: Re: Problems with Slackware 2.0.36
>
> 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 versa
> (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 enforce
> linking against the libc5 libs wich are lying around somewhere?
>
> > Thanks
> > Daniel Sawitzki
>
>
> Arne Hueggenberg
>