Bug#202204: marked as done (xlibmesa3-glu: Symlink missing: libGLU.so -> libGLU.so.1.3)
Your message dated Thu, 24 Jul 2003 15:18:43 -0500
with message-id <20030724201843.GD6121@deadbeast.net>
and subject line Bug#202204: xlibmesa3-glu: Symlink missing: libGLU.so -> libGLU.so.1.3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 20 Jul 2003 20:14:58 +0000
>From ludovic.brenta@insalien.org Sun Jul 20 15:14:56 2003
Return-path: <ludovic.brenta@insalien.org>
Received: from sojef.skynet.be [195.238.2.127]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19eKa8-0001i2-00; Sun, 20 Jul 2003 15:14:56 -0500
Received: from lbrenta (29.14-136-217.adsl.skynet.be [217.136.14.29])
by sojef.skynet.be (8.12.9/8.12.9/Skynet-OUT-2.21) with SMTP id h6KKEqVr021210;
Sun, 20 Jul 2003 22:14:52 +0200
(envelope-from <ludovic.brenta@insalien.org>)
Message-Id: <[🔎] 200307202014.h6KKEqVr021210@sojef.skynet.be>
Received: by lbrenta (sSMTP sendmail emulation); Sun, 20 Jul 2003 22:09:02 +0200
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="UTF-8"
From: Ludovic Brenta <ludovic.brenta@insalien.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: xlibmesa3-glu: Symlink missing: libGLU.so -> libGLU.so.1.3
X-Mailer: reportbug 2.18
Date: Sun, 20 Jul 2003 22:09:02 +0200
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=-5.1 required=4.0
tests=BAYES_00,HAS_PACKAGE,MSG_ID_ADDED_BY_MTA_2
version=2.53-bugs.debian.org_2003_07_20
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_07_20 (1.174.2.15-2003-03-30-exp)
Package: xlibmesa3-glu
Version: 4.2.1-6
Severity: important
The package creates the following symbolic links:
$ ll /usr/lib/libGLU*
lrwxrwxrwx 1 root root 13 2003-05-01 15:14 /usr/lib/libGLU.so.1 -> libGLU.so.1.3
lrwxrwxrwx 1 root root 26 2003-05-01 15:14 /usr/lib/libGLU.so.1.3 ->
../X11R6/lib/libGLU.so.1.3
This makes it impossible to link a program with -lGLU. There should be an
additional symlink named libGLU.so.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux lbrenta 2.4.20-3-686-smp #1 SMP Sat Jun 7 23:35:32 EST 2003 i686
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8
Versions of packages xlibmesa3-glu depends on:
ii libc6 2.3.1-16 GNU C Library: Shared libraries an
ii libgcc1 1:3.3.1-0pre0 GCC support library
ii libstdc++5 1:3.3.1-0pre0 The GNU Standard C++ Library v3
-- no debconf information
---------------------------------------
Received: (at 202204-done) by bugs.debian.org; 24 Jul 2003 20:19:48 +0000
>From branden@deadbeast.net Thu Jul 24 15:18:46 2003
Return-path: <branden@deadbeast.net>
Received: from dhcp065-026-182-085.indy.rr.com (redwald.deadbeast.net) [65.26.182.85]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19fmY0-0002u2-00; Thu, 24 Jul 2003 15:18:44 -0500
Received: by redwald.deadbeast.net (Postfix, from userid 1000)
id 466DD643FD; Thu, 24 Jul 2003 15:18:43 -0500 (EST)
Date: Thu, 24 Jul 2003 15:18:43 -0500
From: Branden Robinson <branden@debian.org>
To: 202204-done@bugs.debian.org
Subject: Re: Bug#202204: xlibmesa3-glu: Symlink missing: libGLU.so -> libGLU.so.1.3
Message-ID: <20030724201843.GD6121@deadbeast.net>
References: <[🔎] 200307202014.h6KKEqVr021210@sojef.skynet.be> <[🔎] 6ufzl16iyx.fsf@zork.zork.net> <[🔎] m3k7acq259.fsf@insalien.org> <[🔎] 6u4r1g7s9k.fsf@zork.zork.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="siaTt5BtGpUbPgBZ"
Content-Disposition: inline
In-Reply-To: <[🔎] 6u4r1g7s9k.fsf@zork.zork.net>
Mail-Copies-To: nobody
X-No-CC: I subscribe to this list; do not CC me on replies.
X-Manoj-Position-Advisory: Please note that Manoj Srivastava likely doubts any facts posited and opposes any conclusions reached in this message.
User-Agent: Mutt/1.5.4i
Delivered-To: 202204-done@bugs.debian.org
X-Spam-Status: No, hits=-21.8 required=4.0
tests=BAYES_10,EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE_2,
QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES,
USER_AGENT_MUTT
autolearn=ham version=2.53-bugs.debian.org_2003_07_20
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_07_20 (1.174.2.15-2003-03-30-exp)
--siaTt5BtGpUbPgBZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, Jul 20, 2003 at 11:22:31PM +0100, Sean Neakums wrote:
> Ludovic Brenta <ludovic.brenta@insalien.org> writes:
>=20
> > Sean Neakums <sneakums@zork.net> writes:
> >
> > Ah, OK. Sorry I didn't know. But then I have a question: how do
> > binaries find the shared lib without the link? i.e. if I ever create
> > a binary with -lGLU, how does the binary find libGLU.so.1.3 if
> > libGLU.so does not exist?
>=20
> Applications are always linked against libFoo.so.N, rather than
> libFoo.so. (Run ldd on some binaries on your system to see this.)
> This is done so that when N is increased, indicating an incompatible
> change in the library's interface, the application will simply fail to
> start, rather than starting and then crashing or otherwise
> misbehaving.
Closing this bug per discussion in the logs.
--=20
G. Branden Robinson |
Debian GNU/Linux | Music is the brandy of the damned.
branden@debian.org | -- George Bernard Shaw
http://people.debian.org/~branden/ |
--siaTt5BtGpUbPgBZ
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iEYEARECAAYFAj8gPyIACgkQ6kxmHytGonxzLwCfeXialqwMy8OoCy2ebHqIAxjo
A+kAmwWmXaazZjPBGd3ck3fOh7CepR9q
=N38P
-----END PGP SIGNATURE-----
--siaTt5BtGpUbPgBZ--
Reply to: