Bug 11163 - mjpegtools -1.6.0-r5 fails to build
|
Bug#:
11163
|
Product: Gentoo Linux
|
Version: 1.4_rc1
|
Platform: x86
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: fisi.tilman.klar@gmx.de
|
Reported By: spider@gentoo.org
|
|
Component: Applications
|
|
|
URL:
|
|
Summary: mjpegtools -1.6.0-r5 fails to build
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2002-11-24 11:53 0000
|
gcc 3.2.1
glibc 2.3.1-r2
MAKEOPTS="-j1"
i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include
-DG_LOG_DOMAIN=\"lavtools\" -DLAVPLAY_VERSION=\"1.6.0\" -I/usr/include -I/usr/inclu
de/glib-1.2 -I/usr/lib/glib/include -I/usr/local/include -I
/mnt/build/portage/mjpegtools-1.6.0-r5/work/mjpegtools-1.6.0/../quicktime4linux-1.4-patch
-I/u
sr/X11R6/include -I /usr/X11R6/include -I../utils -I/usr/include/avifile
-I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11
R6/include -mcpu=i686 -march=i686 -march=i686 -Wall -Wunused -c editlist.c -MT
editlist.lo -MD -MP -MF .deps/editlist.TPlo -fPIC -DPIC -o editlist.o
mv -f editlist.o .libs/editlist.lo
i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include
-DG_LOG_DOMAIN=\"lavtools\" -DLAVPLAY_VERSION=\"1.6.0\" -I/usr/include -I/usr/inclu
de/glib-1.2 -I/usr/lib/glib/include -I/usr/local/include -I
/mnt/build/portage/mjpegtools-1.6.0-r5/work/mjpegtools-1.6.0/../quicktime4linux-1.4-patch
-I/u
sr/X11R6/include -I /usr/X11R6/include -I../utils -I/usr/include/avifile
-I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11
R6/include -mcpu=i686 -march=i686 -march=i686 -Wall -Wunused -c editlist.c -MT
editlist.lo -MD -MP -MF .deps/editlist.TPlo -o editlist.o >/dev/null 2>&1
mv -f .libs/editlist.lo editlist.lo
source='lav_io.c' object='lav_io.lo' libtool=yes \
depfile='.deps/lav_io.Plo' tmpdepfile='.deps/lav_io.TPlo' \
depmode=gcc3 /bin/sh ../depcomp \
/bin/sh ../libtool --mode=compile i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.
-I.. -I.. -I/usr/include -DG_LOG_DOMAIN=\"lavtools\" -DLAVPLAY_VERSION=\"1
.6.0\" -I/usr/include -I/usr/include/glib-1.2 -I/usr/lib/glib/include
-I/usr/local/include -I /mnt/build/portage/mjpegtools-1.6.0-r5/work/mjpegtools-1.6.0
/../quicktime4linux-1.4-patch -I/usr/X11R6/include -I /usr/X11R6/include
-I../utils -I/usr/include/avifile -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2
-I/usr/lib/glib/include -I/usr/X11R6/include -mcpu=i686 -march=i686
-march=i686 -Wall -Wunused -c -o lav_io.lo `test -f lav_io.c || echo './'`lav_io.c
rm -f .libs/lav_io.lo
i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include
-DG_LOG_DOMAIN=\"lavtools\" -DLAVPLAY_VERSION=\"1.6.0\" -I/usr/include -I/usr/inclu
de/glib-1.2 -I/usr/lib/glib/include -I/usr/local/include -I
/mnt/build/portage/mjpegtools-1.6.0-r5/work/mjpegtools-1.6.0/../quicktime4linux-1.4-patch
-I/u
sr/X11R6/include -I /usr/X11R6/include -I../utils -I/usr/include/avifile
-I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11
R6/include -mcpu=i686 -march=i686 -march=i686 -Wall -Wunused -c lav_io.c -MT
lav_io.lo -MD -MP -MF .deps/lav_io.TPlo -fPIC -DPIC -o lav_io.o
lav_io.c: In function `check_DV2_input':
lav_io.c:1385: too many arguments to function `dv_decoder_new'
lav_io.c:1415: warning: implicit declaration of function `dv_decoder_free'
make[2]: *** [lav_io.lo] Error 1
make[2]: Leaving directory
`/mnt/build/portage/mjpegtools-1.6.0-r5/work/mjpegtools-1.6.0/lavtools'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/mnt/build/portage/mjpegtools-1.6.0-r5/work/mjpegtools-1.6.0'
make: *** [all] Error 2
Heyas Spider,
i have exactly the same problem on my box - give me an "emerge info" please.
Thanks,
-phoen][x-
Should be fixed in -r6.
Thanks spider,
-phoen][x-
so why is -r6 marked as unstable ?
Hi,
I ahve exactly same problem. How can I switch btw to unstable, or at the best
get just that -r6 package from unstable? TIA. mmokrejs@natur.cuni.cz
just type
#emerge /usr/portage/media-video/mjpegtools/mjpegtools-1.6.0-r6.ebuild
*** Bug 15385 has been marked as a duplicate of this bug. ***