Your message dated Sun, 10 Aug 2008 04:57:52 +0300
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#453790: libglide2: couldn't find library libglide.so.2
has caused the Debian Bug report #453790,
regarding glide: FTBFS: dpkg-shlibdeps: failure: couldn't find library 
libglide.so.2 needed by debian/glide2-bin/usr/lib/glide2/bin/test05 (its RPATH 
is '').
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
453790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=453790
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: glide
version: 2002.04.10-14
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20071130 qa-ftbfs
Justification: FTBFS on i386

Hi,

During a rebuild of all packages in sid, your package failed to build on i386.

Relevant part:

 > dh_installdirs
 > install -m 755 build-tree/glide2x/h3/glide/tests/test[0-9][0-9] \
 >                         
 > /build/user/glide-2002.04.10/debian/glide2-bin/usr/lib/glide2/bin/
 > install -m 755 build-tree/glide2x/cvg/bin/pass \
 >                         
 > /build/user/glide-2002.04.10/debian/glide2-bin/usr/lib/glide2/bin/
 > dh_strip
 > dh_installdocs
 > dh_installchangelogs
 > dh_link
 > dh_compress
 > dh_fixperms
 > dh_installdeb
 > dh_shlibdeps
 > dpkg-shlibdeps: failure: couldn't find library libglide.so.2 needed by 
 > debian/glide2-bin/usr/lib/glide2/bin/test05 (its RPATH is '').
 > Note: libraries are not searched in other binary packages that do not have 
 > any shlibs file.
 > To help dpkg-shlibdeps find private libraries, you might need to set 
 > LD_LIBRARY_PATH.
 > dh_shlibdeps: command returned error code 512
 > make[1]: *** [binary-glide2-bin-real] Error 1
 > make[1]: Leaving directory `/build/user/glide-2002.04.10'
 > make: *** [binary-glide2-bin] Error 2
 > dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules binary gave error 
 > exit status 2

The full build log is available from:
        http://people.debian.org/~lucas/logs/2007/11/30

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment.  Internet was not accessible from the build systems.

-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED]             GPG: 1024D/023B3F4F |



--- End Message ---
--- Begin Message ---
Source: glide
Source-Version: 2002.04.10-15

On Tue, 2008-08-05 at 20:18:54 +0200, Javier Serrano Polo wrote:
> El dt 05 de 08 de 2008 a les 20:14 +0300, en/na Guillem Jover va
> escriure:
> > > libglide.so.2 is still missing.

> > Hmm, this is not much helpful, missing from where? I can build the glide
> > source package on a sid system just fine.
> 
> This isn't a FTBFS. Perhaps it's unrelated.

The problem you are describing is unrelated to this bug reports.

> libglide2x.so is a broken link to libglide.so.2.
>
> svgalib1-libggi2 depends on libglide2 and applications won't start because
> the linker can't find that library.

The libglide.so.2 symlink should have been setup by the maintainer
scripts. I've it here even on boxes w/o a 3dfx card and I cannot reproduce
installing the package and not getting the symlink created.

Anyway svgalib1-libggi2 does not use glide at all, it's just being
pulled due to the polluted .la files from libggi ...

> Anyway, rebuilding svgalib1-libggi2 gets rid of the libglide2
> dependency.

... which as you say here can be fixed by just rebuilding
svgalib1-libggi2 against latest libggi

Also I see now the bug I filed on libggi about the core library linking
against all module libraries was closed but reappeared again, which is
the real cause all those things are polluting the .la files.

> As I'm not interested in fixing this bug anymore, do you
> think it should be closed?

So closing, but if you can reproduce the incomplete symlink problem,
please open a new bug report!

thanks,
guillem


--- End Message ---

Reply via email to