The build log isn't very useful. I ran "grep -ir 'package\.' /var/lib/dpkg/info/*.symbols" and revealed libegl1-mesa as source for the problem. The head of libegl1-mesa:amd64.symbols is
Is a line that start with a space followed by a # considered as comment? In this case it would be a bug in dpkg-shlibdeps, otherwise it's a bug in mesa.
Here's the build log which runs dpkg-shlibdeps in verbose mode: https:/ /launchpadlibra rian.net/ 83339925/ buildlog_ ubuntu- precise- amd64.vlc_ 1.2.0~~ git20111020% 2Br956- 0~r46~precise1_ FAILEDTOBUILD. txt.gz
The build log isn't very useful. I ran "grep -ir 'package\.' /var/lib/ dpkg/info/ *.symbols" and revealed libegl1-mesa as source for the problem. The head of libegl1- mesa:amd64. symbols is
libEGL.so.1 libegl1-mesa #MINVER# | libegl1-x11 t@Base 7.8.1 ge@Base 7.8.1
# package.
_eglBindContex
_eglBindTexIma
Is a line that start with a space followed by a # considered as comment? In this case it would be a bug in dpkg-shlibdeps, otherwise it's a bug in mesa.