I'm just re-sending this having composed the mail last night and sent it from the wrong account, and the mailling list dumped it!
> Andrew Church wrote: > >>>Looks like the set of Makefiles (and ./configure in the top-level >>>directory) that are checked into CVS are a bit out of date then, >>> >>> >> >> Um, configure and the Makefiles aren't in CVS at all. Are you >>sure you're using the right repository? (: See >>http://www.transcoding.org/cgi-bin/transcode?Download >> >> >> > > The CVS server-site looks OK- > > % cat CVS/Root > :pserver:[EMAIL PROTECTED]:/cvstc > > Most likely I ran 'autoreconf' ages ago, did a "cvs update" recently > and forgot to redo the "autoreconf -i -f" before I tried building, in > which case I'm sorry for wasting your time. > > There's something confusing going on (and this time I *have* run > 'autoreconf', OK? :-)) > Last night at midnight I gave up on realising that I had to load > ffmpeg-devel. Actually, that's midnight the *previous* night now! > (I'm on Fedora Core 4). > Tonight, I've done all that (loaded ffmpeg > ffmpeg-0.4.9-0.3.20051207.2.fc4 from freshrpms along with the matching > -devel package). > > Now I get the following excerpts from the output of './configure' :- > > % cat err.lst > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking target system type... i686-pc-linux-gnu > checking for a BSD-compatible install... /usr/bin/install -c > [.....] > checking for gzopen in -lz... yes > checking for sin in -lm... yes > checking for pkgconfig support for libavcodec... yes > checking how to determine LIBAVCODEC_CFLAGS... pkg-config > checking ffmpeg/avcodec.h usability... yes > checking ffmpeg/avcodec.h presence... yes > checking for ffmpeg/avcodec.h... yes > checking how to determine LIBAVCODEC_LIBS... pkg-config > checking for avcodec_thread_init in -lavcodec... yes > error: transcode needs at least libavcodec 51.9install a cvs version > after 20060814failed > checking for pkgconfig support for libavformat... yes > checking how to determine LIBAVFORMAT_CFLAGS... pkg-config > checking ffmpeg/avformat.h usability... yes > checking ffmpeg/avformat.h presence... yes > checking for ffmpeg/avformat.h... yes > checking how to determine LIBAVFORMAT_LIBS... pkg-config > checking for av_register_all in -lavformat... yes > error: transcode needs at least libavformat 50.5install a cvs version > after 20060814failed > checking for pkgconfig support for libmpeg2... no > checking how to determine LIBMPEG2_CFLAGS... default > checking mpeg2dec/mpeg2.h usability... yes > checking mpeg2dec/mpeg2.h presence... yes > > [..............] > > ---------------------------------------- > Summary for transcode 1.1.0-cvs: > ---------------------------------------- > > > [....] > mjpegtools yes > sdl no > gtk no > imagemagick no > libjpeg yes > bsdav no > iconv yes > > > ERROR: requirement failed: cannot compile ffmpeg/avcodec.h > ffmpeg/avcodec.h can be found in the following packages: > FFmpeg http://www.ffmpeg.org > > ERROR: requirement failed: cannot compile ffmpeg/avformat.h > ffmpeg/avformat.h can be found in the following packages: > FFmpeg http://www.ffmpeg.org > > > > Please see the INSTALL file in the top directory of the > transcode sources for more information about building > transcode with this configure script. > > > This is confusing. Earlier in the printout, we saw: > checking ffmpeg/avcodec.h usability... yes > checking ffmpeg/avcodec.h presence... yes > messages, then finally a complaint about the very same files (These > files being missing originally promped me to install ffmpeg-devel in > the first place). > > I've just noticed that it seems the problem was flagged by the lines: > > error: transcode needs at least libavcodec 51.9install a cvs version > after 20060814failed > > Rather vitally important messages which were almost invisible amongst > the rest of the copious blurb! > > *Come on guys - you *could* have aborted the ./configure script as > soon as you detected something *this* fatal, surely? :-(* > > As you can probably guess - I've solved my own problem during the > writing of this email! > In true confusing fashion, libavcodec is a part of ffmpeg, and I found > an rpm for a post 2006-08-14 version, built it, installed it and > everything is fine now. It's still version ffmpeg 0.4.9 like I > originally had - it's just a newer one! > D'oh, a newer 0.4.9 should be called 0.4.10 if they want to avoid > confusing the *$£# out of everyone! Yeah - I know. Not transcode's > fault - ffmpeg people's fault, but strewth - this sort of thing makes > for unneccessary hard work all round! Oh, and there's no way to know > that libavcodec 51.9 is the specific version in some given packaging > of ffmpeg. I just got lucky there with the date being on the RPM. > > Just thought I'd relay my confusion over the way the error got > reported. I've been a linux hacker for 10 years and a Un*x one for > another 15 before that. If it confuses *me*, it'll sure as hell mess > up a newbie... > > Steve. > As a postscript to all that, I finally got a working 'transcode' which promptly did exactly what I wanted: transcribe an hour-long ".nuv" file to mpeg2 suitable for archiving on a DVD. And it did it really quick too: a 20 min run on a 1.6GHz AMD machine. I'll have to do it again because I need to set the bitrate a bit higher and splice two .nuv files together first, but that's fine. I'm impressed by the performance - DV to mpeg2 usually takes three times the elapsed time of the video using that same machine running 'kino'. Good work, all. Steve
