<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Le 25/12/2016 à 16:31, liyoubdu a écrit :<br>
<blockquote cite="mid:tencent_54599C7928844ED52ABCF446@qq.com"
type="cite">
<div><span style="line-height: 1.5;">Hello vlc team,</span></div>
<div><br>
FYI, during vlc 3.0 configure script execution, AVCODEC checking
fails with the error :<br>
<br>
checking for AVCODEC... no<br>
configure: error: Comparison operator but no version after
package name 'libavutil' in file
'/usr/src/packages/BUILD/vlc-beta-3.0.0/contrib/x86_64-suse-linux/lib/pkgconfig/libavcodec.pc'.
Pass --disable-avcodec to ignore this error.<br>
<br>
libavcodec.pc content is the following:<br>
prefix=/usr/src/packages/BUILD/vlc-beta-3.0.0/contrib/x86_64-suse-linux<br>
exec_prefix=${prefix}<br>
libdir=/usr/src/packages/BUILD/vlc-beta-3.0.0/contrib/x86_64-suse-linux/lib<br>
includedir=<br>
<br>
Name: libavcodec<br>
Description: Libav codec library<br>
Version: 57.30.2<br>
Requires: libavutil >= ,<br>
Requires.private:<br>
Conflicts:<br>
Libs: -L${libdir} -lavcodec -lSDL -lpthread -lvdpau -lX11
-L/usr/src/packages/BUILD/vlc-beta-3.0.0/contrib/x86_64-suse-linux/lib
-lvpx -lm -lpthread -lopenjpeg -DOPJ_STATIC -lmp3lame -lgsm -lm
-lz -pthread<br>
Libs.private:<br>
Cflags: -I${includedir}<br>
<br>
<br>
I guess the bug is coming from the latest git libav repository
update hosted by videolan. Maybe libav developper team is aware
of this issue and it has already been fixed. In that event,
doing a new libav repository update should be good enough.
Otherwise, libav developper team should be advertised, since
this is blocking vlc 3.0 generation.<br>
<br>
I don't follow libav project evolutions, so I don't know where
to post in a more appropriate manner. If you tell me, i can do
that for you.<br>
<br>
<br>
Merry Christmas to you,<br>
Gilles Sabourin<br>
<br>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<</div>
<div>hi, which version is your operating system <span
style="line-height: 1.5;">and ffmpeg version?</span></div>
</blockquote>
Hi,<br>
<br>
My OS is an openSUSE 13.2 LTS, still supported by NOVELL (Support
will end soon, during january 2017). 8 months ago, vlc 3.0 configure
script reported that my automake version was too old. At least v1.15
was needed. This component was also too old for LEAP 42.1 version,
and to avoid issues with proprietary video drivers, I haven't
replaced my distribution by Tumbleweed rolling release. Instead, I
picked latest automake package from tumbleweed repository and i have
replaced it manually.<br>
<br>
vlc 3.0 generation used to work well until recently last december,
23rd. Better, I even got a vlc 3.0 binary on my tower and I have
launched also generation on my laptop which has stopped with this
error. To check back, I have simply launched a new generation on my
tower without updating anything, but only rebuilding contributions.
Generation failed during vlc 3.0 configure check.<br>
<br>
I think that libav is generated during contributions phase by
default, not ffmpeg. Your question about ffmpeg version seems to me,
irrelevant : <span id="result_box" class="" lang="en"><span
class="">If you carefully looked at the path where the configure
script is complaining about a missing version for libavutil, you
see that it is pointing to the rpm package generation folder,
and not inside any system path.<br>
<br>
I'm pretty confident that the root cause of the issue is coming
from the ffmpeg contribution. These libraries are also generated
and updated from a git repository inside videolan.<br>
<br>
Let's have a look at : /vlc/contrib/src/ffmpeg/rules.mak<br>
</span></span>The main function of this script, provided by vlc
developers is to download a tarball archive or a git tree and to
compile ffmpeg libraries. Script is beginning by :<br>
<br>
# FFmpeg<br>
<br>
#Uncomment the one you want<br>
#USE_LIBAV ?= 1<br>
#USE_FFMPEG ?= 1<br>
<br>
ifdef USE_FFMPEG<br>
FFMPEG_HASH=HEAD<br>
FFMPEG_SNAPURL :=
<a class="moz-txt-link-freetext" href="http://git.videolan.org/?p=ffmpeg.git;a=snapshot;h=$(FFMPEG_HASH);sf=tgz">http://git.videolan.org/?p=ffmpeg.git;a=snapshot;h=$(FFMPEG_HASH);sf=tgz</a><br>
FFMPEG_GITURL := <a class="moz-txt-link-freetext" href="http://git.videolan.org/git/ffmpeg.git">http://git.videolan.org/git/ffmpeg.git</a><br>
else<br>
FFMPEG_HASH=HEAD<br>
FFMPEG_SNAPURL :=
<a class="moz-txt-link-freetext" href="http://git.libav.org/?p=libav.git;a=snapshot;h=$(FFMPEG_HASH);sf=tgz">http://git.libav.org/?p=libav.git;a=snapshot;h=$(FFMPEG_HASH);sf=tgz</a><br>
FFMPEG_GITURL := git://git.libav.org/libav.git<br>
endif<br>
[...]<br>
<br>
Both variables are commented, so the script will pick git libav.org
repository to the head, not git videolan.org repository, instead of
what I wrongly wrote in first message. Remark that this approach is
a bit risky since a problem localized in ffmpeg development can lead
to vlc generation failure. Developers organizations may have found
interesting to check both developments at a time since most of audio
/ video formats processing for vlc relies intensively on ffmpeg
libraries.<span id="result_box" class="" lang="en"><span class=""></span></span><br>
<br>
I haven't look closely at the git libav tree. I guess that
libavcodec.pc file is coming from libavcodec.pc.in file where not
all fields were well replaced by autotool generation chain. <br>
<br>
Best,<br>
Gilles<br>
</body>
</html>