bloxwichkiwi wrote: ↑
Fri May 18, 2018 11:04 am
Checking for Libav/FFmpeg library versions : not found any of is_ffmpeg, is_libav
Unable to find development files for some of the required FFmpeg/Libav libraries. You need at least FFmpeg 3.2.2 or Libav 12. Aborting.
From just one tiny clue, I can tell your system is UNORTHODOX
– or totally messed up!
That tiny clue is your command prompt.
On a completely "normal" Raspbian system, your command prompt while inside the mpv build directory should look EXACTLY
[email protected]:~/FFmpeg_Build/mpv-0.27.0 $
If I enter the pwd command in this location on my perfectly normal system, I get this:
The pwd command stands for "print working directory" – although conceptually, I prefer to think of it as the "present working directory". It shows the FULL, EXPLICIT PATH that Terminal is currently located in.
But in your case, your command prompt says this:
[email protected]:/FFmpeg_Build/mpv-0.27.0 $
If you compare your command prompt to mine and look very carefully, you'll notice the little squiggly tilde symbol (~) is missing from your path. The tilde symbol acts as an abbreviation for your home directory – which on any "normal" Raspberry system is /home/pi. To the untrained eye, it may be "just a little symbol". But it actually has HUGE implications.
On your system, if you run the pwd command while Terminal is inside the mpv build folder, it will say this:
That means something astounding – you placed the FFmpeg_Build folder at the ROOT
level of your system! That means it exists at "/" instead of "/home/pi". This is definitely NOT an acceptable practice. The root has special properties and is intended "for system use only" – it's definitely not a location for you to be placing source code build folders. Among other things, it's not even owned by the user named "pi" – instead, it's owned by the user named "root". As a result, when logged in normally as user "pi", it has completely alien permissions. That means in Step 4 of my tutorial, you would have needed to deviate from my instructions by using "sudo mkdir FFmpeg_Build" instead of "mkdir FFmpeg_Build" to create the folder in the first place! Otherwise, you would have encountered a "permission denied" error message. By using "sudo", that also means the FFmpeg_Build folder would automatically be owned by root, not pi. Given my detailed instructions, my tutorial has every right to assume that folder is owned by pi – yet in your case, it would be owned by root.
Not to sound like a scolding professor, but this alone tells me that at least to some degree, you decided to do things "your own way". Not a good idea – especially when you consider how complicated and utterly unforgiving it is to build MULTIPLE programs from raw source code. And just to cover myself: Maybe you didn't encounter a permissions issue and therefore didn't have to use "sudo". Well, that would be equally messed up – because that would mean you previously made a completely non-standard, fundamental alteration to your root's permissions.
The missing tilde symbol also means you either don't have a normal home directory (which means you "tampered" with your system) – or for some reason, you do have a home directory (perhaps even /home/pi) – but, as already mentioned, you chose to do things your own way and created the build folder right off your root. My instructions clearly say to open Terminal – which, by default, will automatically open inside your home directory (/home/pi) on any standard, unaltered Raspbian system.
As you may have noticed, I repeatedly emphasized throughout my tutorial that your system must be completely "standard" and "normal" – I even defined those terms in great detail.
As if that weren't enough, I can tell something else from your command prompt – your host name is also unorthodox and non-standard.
Your host name is "hollandpi". On a normal system, it should simply be "raspberrypi". I'm not saying there's anything technically "wrong" about that in and of itself. After all, people are free to alter their host names – or do anything else they wish with their Raspberries!
But my point is that these unusual arrangements don't "just happen". They tell me that you're either an advanced user doing advanced things and thereby creating an unorthodox system in the process – or you're mostly just a regular user trying to do "advanced" things without really understanding their implications!
Either way, it spells trouble. It's a clear "violation" of my tutorial's well-defined rules that emphasize normality and standardization – so I'm not at all surprised that you're having problems. Since I'm able to extract all this concerning information from just a single command prompt, it makes me justifiably suspicious about other unknown "tweaks" you've probably made as well.
You also took it upon yourself to experiment with the wscript file. I realize you probably did that only after you encountered problems. But trust me – my version is the only correct one. By altering the script and leaving out SEVERAL critical elements, you were only digging an even deeper hole for yourself. Remember – everything in my tutorial has been thoroughly tested and proven to work. There's no legitimate reason to change ANYTHING!
Finally, be aware that just because your problems MANIFESTED
in Step 12 does not necessarily
mean that the SOURCE
of your problems have anything to do with Step 12! For example, since mpv is totally dependent on my customized build of the FFmpeg engine in Step 11, even the slightest mistake in building FFmpeg can easily result in errors that only manifest later on while building mpv in Step 12. The untrained observer might therefore think "oh gee – what's wrong with mpv?" When in fact, the question itself is not even right!
Then again, FFmpeg might be perfectly fine. In many cases, the primary error you report – "Checking for Libav/FFmpeg library versions : not found any of is_ffmpeg" – can easily be caused by accidentally skipping the "export LIBRARY_PATH=/opt/vc/lib" line in my mpv build instructions. That essential line comes immediately after the wscript editing phase in my procedure – so it's entirely possible that you got distracted by your edits of the wscript file and accidentally skipped over that critical export command. I'm NOT saying that's what happened – your error messages are generic enough that several other possibilities exist.
No matter what your particular circumstances, however, there's really only one big thing to remember – when followed to the letter
, my tutorial is proven to work.
BOTTOM LINE: Try a "tactical nuke" on the mpv build folder and see what happens. If that doesn't work, you'll need to do a "strategic nuke" on your entire system! I'm strongly guessing you'll need the latter.
What do I mean by tactical and strategic nukes? See my detailed troubleshooting guide that I wrote for someone else – it explains almost EVERYTHING you need to know. It also covers almost every conceivable mistake and oversight someone could possibly make on my tutorial: