[mjpegtools] - [compile prob's]

phex^ · n00b Joined: 21 Nov 2002 Posts: 20

Aye, sup sup fellow gentoo brethren. I'm havin a problem compilin mjpegtools. Now, im no C/C++ expert or novice for that matter, but i know that debuggin compile's normally deals with havin some knowledge in those two languages.. So im gonna post my error and hopefully someone could hook me up with a solution

---------------------------------------------
/include -I/usr/X11R6/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
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]: *** Waiting for unfinished jobs....
mv -f .libs/editlist.lo editlist.lo
make[2]: Leaving directory `/var/tmp/portage/mjpegtools-1.6.0-r5/work/mjpegtools-1.6.0/lavtools'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/mjpegtools-1.6.0-r5/work/mjpegtools-1.6.0'
make: *** [all] Error 2

!!! ERROR: media-video/mjpegtools-1.6.0-r5 failed.
!!! Function src_compile, Line 88, Exitcode 2
!!! (no error message)
----------------------------------------------
hopefully someone can hlp me out, thx

karl11 · Guru Joined: 25 Jun 2002 Posts: 469 Location: Raleigh, NC

emerge the r6 version of mjpegtools...it's masked, but you probably have quicktime set as a USE flag, in which case you need r6.

Karl

panix · n00b Joined: 17 Dec 2002 Posts: 5

this is actually a problem with the calls to the libdv library.

The solution is to edit the lav_io.c and lav_common.c files in the lavtools directory. look for dev_decoder_new(0,0,0) and change it to dev_decoder_new().

That makes it compile.

phex^ · n00b Joined: 21 Nov 2002 Posts: 20

hrm.. neither of those worked, but i just went to the ww site and d/l'd and built the most recent version of mjpegtools. now everything is working fine

panix · n00b Joined: 17 Dec 2002 Posts: 5

hmm. dunno. worked for me (i actually just pulled that from the ebuild file for mjpegtools, they patch those 2 files for some reason, but with libdv >=0.95 you arent suppossed to have to do that i dont believe).

glad ya got it working!

kraaij · Posted: Thu Jan 09, 2003 8:31 pm Post subject:

I had the same problem trying to emerge mjpegtools-1.6.0-r7. What fixed it for me was compiling without quicktime in my use flags, so:

Q · Posted: Mon Jan 27, 2003 12:37 pm Post subject:

None of the solutions here worked for me. I found the issue to be CFLAGS. Mine were quite aggressive. When I used the default pentium4 03 and -pipe it compiled fine

Loke · Apprentice Joined: 25 May 2002 Posts: 274 Location: Norway

How come when I try to merge jmpegtools-r7 (or r5 or r6 for that matter), it looks for an arts lib in /usr/kde/3/lib/ whereas I only got /usr/kde/3.1/lib..? The file its looking for do exist btw, but Im still wondering why it looks in /usr/kde/3/ ? Been a while since I had anything in /usr/kde/3/

Delphiki · Guru Joined: 04 Oct 2002 Posts: 337 Location: A2

I had the same problem about it looking in the kde-3 directory. I'd already removed anything before kde-3.1 so I made a symlink from /usr/kde/3.1 to /usr/kde/3 for the duration of the build and that fixed the problem. I would assume this is just a bug in the makefile or ebuild where someone didn't take into consideration that kde-3.1 might be installed.
_________________
Excellent..

JohnY · Guru Joined: 26 Jul 2002 Posts: 305

In my case -r7 didn't like either -march=k6 or -mcpu=k6 (gcc 2.95.3) with my K6-III+, but it compiled with -quicktime and -mcpu=i586.

Hmmm,

JohnY