Error Libavformat
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about libavformat.so.53 => not found Stack Overflow the company Business Learn more about hiring developers or posting ads with unable to locate package libavformat53 us Raspberry Pi Questions Tags Users Badges Unanswered Ask Question _ Raspberry Pi Stack Exchange is a question and answer site
Libavformat.so.53: Cannot Open Shared Object File: No Such File Or Directory
for users and developers of hardware and software for Raspberry Pi. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best
E: Unable To Locate Package Libavformat53
answers are voted up and rise to the top Raspberry pi camera module libavformat up vote 0 down vote favorite I have a camera module connected to my raspberry pi and have followed these instructions to make it work for a stream: Installation guide I type this command to test it: ./motion -n -c motion-mmalcam.conf But I get this error : ./motion: error while loading shared libraries: libavformat.so.53: cannot open libavformat53 jessie shared object file: No such file or directory And yes I have installed libjpeg62. The package for libavformat53 doesn't even exist. There seems to be no resolution to this problem. EDIT: output for ldd motion Shows: libpq.so.5 => not found libavformat.so.53 => not found libavcodec.so.53 => not found libavtil.so.51 => not found python linux camera share|improve this question asked Mar 24 at 7:21 DorianT 13 migrated from stackoverflow.com Mar 24 at 14:36 This question came from our site for professional and enthusiast programmers. add a comment| 1 Answer 1 active oldest votes up vote 0 down vote Try install this package: sudo apt-get install libavformat-dev More details about your problem you can find at: https://www.raspberrypi.org/forums/viewtopic.php?f=91&t=123397 share|improve this answer answered Mar 24 at 14:43 Huczu 66519 Tried it but didn't work. –DorianT Mar 24 at 16:09 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Not the answer you're looking for? Browse other questions tagged python linux camera or a
ffmpeg shared object libavformat.so Test case Ensure that ffmpeg is not installed in the standard directory. Build ffmpeg with a non-standard installation directory build motion with option --with-ffmpeg=/dir
Motion-mmal Jessie
Start motion. The following run-time error is displayed: motion: error while loading unable to locate libavformat53 shared libraries: libavformat.so: cannot open shared object file: No such file or directory Attempting the same test-case for motion-3.2.1 raspberry pi jessie motion produces no error. Environment Motion version: 3.2.2_snap9 ffmpeg version: 0.4.9pre1 Shared libraries: curl, xmlrpc, ffmpeg, mysql, postgresql Server OS: RedHat, kernel 2.4 -- BruceDurham - 04 Aug 2005 Follow up http://raspberrypi.stackexchange.com/questions/44617/raspberry-pi-camera-module-libavformat A couple of questions: What does ldd motion give you? I.e., do libavformat.so and libavcodec.so get resolved (I guess not)? Is the non-standard ffmpeg library folder (i.e., /dir/lib to go with your example) in /etc/ld.so.conf? Does it appear when you run ldconfig -v? I would guess that putting the library folder in /etc/ld.so.conf and running ldconfig would do the trick. I http://www.lavrsen.dk/foswiki/bin/view/Motion/BugReport2005x08x04x220823 don't know about RH, but in Gentoo you're not supposed to edit /etc/ld.so.conf directly, but should put files in /etc/env.d instead. Anyway, make sure your newly added library path occurs before any other path that includes an ffmpeg installation (e.g., one in /usr/local/lib). Generally speaking, Motion does not handle multiple installations of FFMpeg very well, in particular if some are in the ordinary search paths (e.g., /usr/lib or /usr/local/lib) and others are in custom folders. This is, however, a problem with how runtime linking is performed in general and not something that we can blame Motion for. Why it worked for you in a previous version of Motion, I don't know. A solution to the problem is to edit the makefile and hard-code the paths to libavformat.so and libavcodec.so (off the top of my head, something in line with -l/usr/local/lib/ffmpeg-custom/lib/libavformat.so, but this is neither very elegant nor very flexible. Plus it requires some clumsy additions to the configure script if we want it to happen automatically, if I recall correctly. -- PerJonsson - 06 Aug 2005 This for sure not a
allformats & libavformat error? Reported by: virtuali Owned by: https://trac.ffmpeg.org/ticket/54 michael Priority: normal Component: ffmpeg Version: git http://www.joakimlahtinen.se/2016/installing-motion-on-raspberry-pi-2-jessie/ Keywords: Cc: Blocked By: Blocking: Reproduced by developer: no Analyzed by developer: no Description Hi, I am trying to compile with the latest git rep for ffmpeg unable to and I am getting the following errors: make[1]: * [allformats.o] Error 1 make[1]: Leaving directory `/usr/src/ffmpegscript/mplayer/ffmpeg/libavformat' make: * [ffmpeg/libavformat/libavformat.a] Error 2 cp: cannot create regular file `/usr/local/ffmpeg/etc/mplayer/codecs.conf': No such file or directory Would anybody know unable to locate why this is happening or a fix for it? Cheers. Oldest first Newest first Threaded Comments only Change History (1) comment:1 Changed 6 years ago by cehoyos Priority changed from important to normal Resolution set to invalid Status changed from new to closed This looks like a problem with MPlayer (actually a MPlayer-related script that I do not know). Please re-open if you have a problem with the current FFmpeg snapshot. Note: See TracTickets for help on using tickets. Download in other formats: Comma-delimited Text Tab-delimited Text RSS Feed Powered by Trac 1.0.1 By Edgewall Software. Visit the Trac open source project athttp://trac.edgewall.org/
on Raspberry Pi 2 Jessie March 6, 2016September 21, 2016 by Joakim Lahtinen Installing Installing Motion on the Jessie dist is not completely straight forward. When installing it through apt-get like normally, you will see something like the following in the logs: Note, selecting ‘libjpeg62-turbo’ instead of ‘libjpeg62’ It turns out that the Jessie dist is using a different libjpeg library than the Wheezy dist, which causes some issues when trying to run Motion. The error log will contain the following: ./motion: error while loading shared libraries: libavformat.so.53: cannot open shared object file: No such file or directory So what you need to do is the following; first install all dependencies manually: sudo apt-get install -y libjpeg-dev libavformat56 libavformat-dev libavcodec56 libavcodec-dev libavutil54 libavutil-dev libc6-dev zlib1g-dev libmysqlclient18 libmysqlclient-dev libpq5 libpq-dev Then download and untar this modified Motion release: wget https://www.dropbox.com/s/6ruqgv1h65zufr6/motion-mmal-lowflyerUK-20151114.tar.gz
tar -zxvf motion-mmal-lowflyerUK-20151114.tar.gz (The source for this package can be found at https://github.com/lowflyerUK/motion/tree/mmal-test) And then to start the program, run: sudo ./motion -c motion-mmalcam-both.conf Done! Categories DevTags Raspberry Pi Post navigation Installing Go on Raspberry Pi 2 and creating a simple file server Bigben Play Wireless Controller (Wii U Pro controller) review 20 thoughts on “Installing Motion on Raspberry Pi 2 Jessie” Ben April 28, 2016 at 16:43 | Reply Thanks! tranzistor May 18, 2016 at 08:57 | Reply oh yeah! Multumesc! Joyce May 26, 2016 at 19:37 | Reply Wow, you solved my issue in 3 minutes, that I had been troubleshooting for 2 days. Thanks so much! Bill June 9, 2016 at 19:54 | Reply Cannot get more than 5M out of new 8Meg camera with Motion. Picam.py will go the 3280 x 2464. Have others got it working? Thanks for the Jessie version. Isaac June 28, 2016 at 06:59