clone 319096 -1 reassign -1 libavcodec-dev retitle -1 libavcodec-dev: Illegal instruction in Altivec check on non-Altivec machines thanks
On Wed, Jul 20, 2005 at 09:20:45AM +0200, Jeff Williams wrote: > Paul Brossier wrote: > >On Tue, Jul 19, 2005 at 11:16:11PM +0200, Jeff Williams wrote: > >>Kino dies on start up saying 'Illegal instruction'. Doing an strace > >>gives: (...) > >it runs fine on my powerpc. could you make a gdb backtrace? > > > Hmm, do you have a g4? Seems to be something to do wiith altivec. > > Program received signal SIGILL, Illegal instruction. > [Switching to Thread 16384 (LWP 19430)] > 0x1016220c in has_altivec () > (gdb) bt > #0 0x1016220c in has_altivec () > #1 0x10163fe0 in dsputil_h264_init_ppc () > #2 0x10161330 in dsputil_init_ppc () > #3 0x100e0914 in dsputil_init () > #4 0x101471a4 in dvvideo_init () > #5 0x100dcff4 in avcodec_open () > #6 0x10066bdc in Frame (this=0x303f5008) at frame.cc:94 (...) Thanks for the backtrace. The illegal instruction is hit in code from ffmpeg's libavcodec. I take it that you're running on a g3 or similar, so apparently the check for Altivec support is broken on machines without Altivec. I'm duplicating this bug to libavcodec-dev, therefore. kino will need to be rebuilt on ppc to pick up the fix. > PS. My apt-get doesn't do build-deps. What version does that? It would > be pretty handy. That was a typo in Paul's message. The correct command is 'apt-get build-dep <pkgname>'. Regards, Daniel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
