Several other "RESOLVED" bugs state FFMpeg-xvidcap build problem is fixed - unfortunately, for the current versions of FFMpeg, it's not. I'm very new to linux, or else I would look to getting the old patch updated to the new version of FFMpeg, but at the moment I fixed it by masking out all older versions of FFMpeg. That being said, masking the older version did not solve the problem at first - XVidcap then compiled, but Segmentation Fault'ed every time it was run command-line (and when recording began every other time). I'm afraid I don't know exactly what fixed this for me (I tried many things), but I BELIEVE manually installing LAME (mpeg encoder) was the trick. Perhaps the xvidcap makefile is including the wrong LAME directory? Reproducible: Always Steps to Reproduce: 1.emerge ffmpeg xvidcap 2.>BUILD FAILS< Actual Results: At least one error (there were many) was: "motion_est.c:178: warning: 'uvdxy' might be used uninitialized in this function" though I believe the real culprit was a line about FFMpeg functions. Expected Results: Build succesfully, incorporating the FFMpeg-Xvidcap patch for the current version of both programs. Portage 2.0.52-r1 (default-linux/amd64/2005.0, gcc-3.4.4, glibc-2.3.5-r1, 2.6.13-gentoo x86_64) ================================================================= System uname: 2.6.13-gentoo x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.12.0_pre8 dev-lang/python: 2.3.5, 2.4.1-r1 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -O2" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde /3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -O2" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.ccccom.com ftp://gentoo.netnitco.net/pub/mirrors/gentoo/source/ http://mirror.clarkson.e du/pub/distributions/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="amd64 X alsa apache2 avi bash-completion berkdb bitmap-fonts cdr crypt cups curl doc dvd dvdread eds emboss emul- linux-x86 encode esd fam foomaticdb fortran ftp gif gpm gstreamer gtk gtk2 i8x0 imagemagick imlib ipv6 java jpeg kde l ibwww lzw lzw-tiff motif mp3 mpeg mysql ncurses nls nvidia opengl pam pdflib perl png python qt quicktime readline sdl sound spell ssl symlink tcpd tiff truetype truetype-fonts type1-fonts usb userlocales videos xine xml2 xmml xmms xpm xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Excuse me - I masked out all NEWER versions of FFMpeg. Also worth note is that I have an AMD64 system, and use ~amd64, as you can see in the above info. I beieve this error is cross-platform, though. One more thing - the stated "motion_est.c:178: warning: 'uvdxy'" error mentioned above is probably fromm FFMpeg's emerge, not xvidcap's. I apologize. If you believe the specific error message is critical, I will un-fix my installation and retrieve it. Finally, I'd like to apologize - when I tried to set one of the previous bugs to be OPEN again, I couldn't change the box at the top of the page. I failed to notice the reassign bug function. Let this be my warning.
We really can't guess. Post/attach actual error messages and ffmpeg version as well and reopen then, please.