Your message dated Sun, 29 Apr 2012 16:38:06 +0200
with message-id
<caj0cceb9fppva+yfa4smnv-34-f0x5l8ocdrs1c2bsfmpiu...@mail.gmail.com>
and subject line Re: Bug#664819: libav source build needs to link with -lgcrypt
has caused the Debian Bug report #664819,
regarding libav source build needs to link with -lgcrypt
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 ow...@bugs.debian.org
immediately.)
--
664819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664819
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libav
Version: 4:0.8.1-1
Severity: normal
gcc -Llibavcodec -Llibavdevice -Llibavfilter -Llibavformat -Llibavutil
-Llibpostproc -Llibswscale -Wl,--as-needed -Wl,--warn-common
-Wl,-rpath-link=libpostproc:libswscale:libavfilter:libavdevice:libavformat:libavcodec:libavutil
-o ffmpeg ff
mpeg.o cmdutils.o -lavdevice -lavfilter -lavformat -lavcodec -lpostproc
-lswscale -lavutil -ldl -lX11 -lXext -lXfixes -lcdio_paranoia -lcdio_cdda
-lcdio -ljack
-lasound -ldc1394 -lraw1394 -lxvidcore -lx264 -lvpx -lvpx -lvorbisenc -lvorbis
-logg -ltheoraenc -ltheoradec -logg -lspeex -lschroedinger-1.0 -lrtmp -lz
-lgnutl
s -lpulse-simple -lpulse -lopenjpeg -lopencv_core -lopencv_imgproc -lopencv_high
gui -lopencv_ml -lopencv_video -lopencv_features2d -lopencv_calib3d -lopencv_obj
detect -lopencv_contrib -lopencv_legacy -lopencv_flann -lmp3lame -lgsm -lfreetyp
e -ldirac_encoder -ldirac_decoder -lstdc++ -lgnutls -lva -lm -pthread -lbz2 -lz
/usr/bin/ld.bfd.real: libavformat/libavformat.a(network.o): undefined reference
to symbol 'gcry_control@@GCRYPT_1.2'
/usr/bin/ld.bfd.real: note: 'gcry_control@@GCRYPT_1.2' is defined in DSO /lib/li
bgcrypt.so.11 so try adding it to the linker command line
/lib/libgcrypt.so.11: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
make[1]: *** [ffmpeg] Error 1
make[1]: Leaving directory `/home/dave/debian/libav/libav-0.8.1/debian-static'
make: *** [build-stamp-static] Error 2
The following allows a successful build:
--- rules.save 2012-03-18 14:40:11.000000000 -0400
+++ rules 2012-03-20 19:08:22.000000000 -0400
@@ -46,6 +46,7 @@
dh_testdir
mkdir -p debian-$*
cd debian-$* && CFLAGS="$(CFLAGS)" CPPFLAGS="$(CPPFLAGS)"
LDFLAGS="$(LDFLAGS)" $(CURDIR)/configure \
+ --extra-libs=-lgcrypt \
$($*_build_confflags) $(extra_$*_build_confflags)
touch $@
-- System Information:
Debian Release: wheezy/sid
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hppa (parisc64)
Kernel: Linux 3.2.11+ (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
On Sun, Apr 29, 2012 at 4:29 PM, John David Anglin <dave.ang...@bell.net> wrote:
>
> On 29-Apr-12, at 4:40 AM, Reinhard Tartler wrote:
>
>> On Thu, Mar 22, 2012 at 1:30 AM, John David Anglin <dave.ang...@bell.net>
>> wrote:
>>>
>>> On 20-Mar-12, at 9:54 PM, Andres Mejia wrote:
>>>
>>>> This issue is common if you're using the libav-extra libraries. It's
>>>> likely a broken symlink from your *.so files.
>>>
>>>
>>>
>>> I don't think so. Updating libgcrypt11 to 1.5.0-3 fixes the build.
>>> Somehow,
>>> it eliminates the dependency.
>>
>>
>> I'm not sure if I understand your message. Does this mean that there
>> is nothing to do in libav and we can close this bug?
>
>
>
> In the original report, there wasn't a broken symlink but I'm puzzled
> by the message:
>
>
> /lib/libgcrypt.so.11: could not read symbols: Invalid operation
>
> Yet the linker seems to have read the symbols:
> /usr/bin/ld.bfd.real: note: 'gcry_control@@GCRYPT_1.2' is defined in DSO
> /lib/libgcrypt.so.11 so try adding it to the linker command line
> Note the undefined reference came from libavformat/libavformat.a(network.o).
> I think
> that libraries need to be explicitly specified on the command line when
> linking with archive libraries.
> I don't know why the archive version of libavformat was used.
>
> With libgcrypt11 1.5.0-3, I had a successful build of the libav package.
> There isn't a reference to the
> above symbol in my installed version of libavformat.a.
>
> Given that issue that triggered the problem is gone, I would close.
Thanks for getting back. I'm closing with this message.
--
regards,
Reinhard
--- End Message ---
_______________________________________________
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
