Re: [Motion-user] Minor problem with motion-3.2.3 on Ubuntu Breezy

[Angel C. <ac...@te...>]

El mi=E9, 14-12-2005 a las 13:27 -0500, jmb365 escribi=F3:
> I have been running motion-3.1.19 under FC2 successfully for over a=20
> year, but now I am trying to run motion-3.2.3 on an Ubuntu Breezy Badger=20
> Pentium 233 and I get:
>=20
> # /usr/bin/motion
> Illegal instruction
>=20
> I am using the latest spca5xx-20051105 USB driver for an X10 camera &=20
> "spcaview -d /dev/video0 -g" works fine.  I do get a video display.  So=20
> I know my /dev/video0 is working ok.

Well not necessary means that won't have problems with motion , because
i guess that in the past the spca5xx module had weird problems, anyway
doesn't seems the problem.

> I have solved this problem and am posting the partial solution here, in=20
> case somebody else runs into the same problem.  I had installed motion=20
> earlier using "apt-get install motion" which apparently is faulty.
>=20
> First install libavcodec-dev & libavformat-dev using "synaptic".  These=20
> provide the ffmpeg libraries needed during the compile process. =20

I've tested motion-3.2.3 that is available from ubutun breezy repository
and i wasn't able to reproduce your problem.

motion-3.2.3-0ubuntu1
libavcodec-dev-0.cvs20050918-4ubuntu1
libavformat-dev-0.cvs20050918-4ubuntu1
kernel 2.6.12-9-k7


Could you send your motion.conf & threadx.conf files ?

> Also=20
> compile & install=20
> "ffmpeg-cvs-20050813-certified-with-motion-3.2.2.tar.gz" from=20
> http://easynews.dl.sourceforge.net/sourceforge/motion/ffmpeg-cvs-20050813=
-certified-with-motion-3.2.2.tar.gz.
>=20
> Obtain=20
> "http://easynews.dl.sourceforge.net/sourceforge/motion/motion-3.2.3.tar.g=
z".=20
> Upon recompiling from source code (./configure && make && make=20
> install). =20

So you install a ffmpeg version from source without removing the one
that comes with ubuntu ?=20

How did you compile it ?=20

Because  unless you compile ffmpeg with prefix=3D/usr or you specified
--with-ffmpeg=3D to compile motion with the new ffmpeg path ,  motion was
compiled with the ubuntu ffmpeg package.

> Remember to copy the freshly compiled "motion" over the=20
> previous "/usr/local/bin/motion"

[snip]

> JMB
>=20
> -------------------------------------------------------------------------=
---------------------------------------------------------------------------
> Debug output is below:
>=20
> # gdb /usr/bin/motion
> GNU gdb 6.3-debian

[snip]

> (gdb) r
> Starting program: /usr/bin/motion
> (no debugging symbols found)
> [Thread debugging using libthread_db enabled]
> [New Thread -1213827392 (LWP 22474)]
> (no debugging symbols found)
> Program received signal SIGILL, Illegal instruction.
> [Switching to Thread -1213827392 (LWP 22474)]
> 0x08050bed in ?? ()
> (gdb) bt
> #0  0x08050bed in ?? ()
> #9  0x082c1463 in _IO_stdin_used ()
> #10 0xb7ff0b30 in _dl_rtld_di_serinfo () from /lib/ld-linux.so.2
> #17 0xb7ff53ce in __libc_memalign () from /lib/ld-linux.so.2
> Previous frame inner to this frame (corrupt stack?)

gdb output doesn't help much or maybe ... yes ! .

I've downloaded the source deb package and i found the problem :

the maintainer/s of ubuntu motion package forgot to add in rules file:

--without-optimizecpu=20

And the package is compile with :

-march=3Dpentium4 -mfpmath=3Dsse -msse2  -mmm

So that's why the motion failed .

I'll send him a email about this issue .

Cheers,

--=20
Angel Carpintero
ack ( at ) telefonica ( dot ) net

Key fingerprint =3D 3FD3 9C90 149E 7824 CECD  6BCF AC2C CA61 6EF1 B90D

"No basta saber, hay que aplicar lo que se sabe;=20
no basta querer hacerlas cosas, hay que hacerlas".

"Knowing is not enough; we must apply.=20
 Willing is not enough; we must do"

 Johann Wolfgang von Goethe