Bug#21408: This is actually a dpkg-shlibdeps bug

[gsstark@mit.edu (Gregory S. Stark)]

This is actually caused by the alpha build engines not having a fixed version
of dpkg-shlibdeps. The patch is below, I reported this bug 213 days ago,
according to the BTS.

I'll merge this bug into the dpkg-shlibdeps bug.

--- dpkg-shlibdeps.orig Mon Apr  6 23:37:09 1998
+++ dpkg-shlibdeps.hacked       Mon Apr  6 23:37:17 1998
@@ -99,10 +99,10 @@
            $nthisldd++;
        } elsif (m,\s+statically linked(\s+\(ELF\))?$,) {
            $nthisldd++;
-       } elsif (m,^\s+(\S+)\.so\.(\S+)\s+=>\s+(/\S+)(\s+\(0x.+\))?$,) {
+       } elsif (m,^\s+(\S+)\.so\.(\S+)\s+=>\s+(/\S+)?,) {
            push(@libname,$1); push(@libsoname,$2); push(@libpath,$3);
            push(@libf,$execf[$i]);
-           push(@libpaths,$3) if !$libpathadded{$3}++;
+           push(@libpaths,$3) if defined($3) && !$libpathadded{$3}++;
            $nthisldd++;
        } else {
            &warn("unknown output from ldd on \`$exec[$i]': \`$_'");