LinuxQuestions.org - [SOLVED] VLC on ARMEDSlack compile fails

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - VLC on ARMEDSlack compile fails (https://www.linuxquestions.org/questions/slackware-14/vlc-on-armedslack-compile-fails-901039/)

VLC on ARMEDSlack compile fails

Compiling VLC using Bob's build script (which is a work of art BTW) on ARMEDSlack errors looking for a52 libs. the error is as follows:

Code:

checking for a52.h in /tmp/build/tmp-vlc/a52dec-0.7.4/include... yes

checking for a52_free in -la52... no

configure: error: the specified tree hasn't been compiled

grep: vlc-config: No such file or directory

sed: can't read vlc-config: No such file or directory

I've googled 'til I'm blue and tried all that I can think of. I just don't understand compiling well enough to solve this one.

If this thread is better placed on another board, let me know. This has always been the best place to go for anything Slackware but this is my first Arm installation.

Thanks,
Bert

Please dp not call my vlc.SlackBuild a "slacky VLC". I was drawn to this thread for the wrong reasons. The "slacky build" is at http://repository.slacky.eu/slackwar...ultimedia/vlc/ and it is not at all the same thing.

Eric

My sincere apologies. I don't know what possessed me to use that nomenclature. I have been fiddling with options so far to no avail and was hoping that someone could help. Once again, sorry for the confusion.

Well, the error you see looks to be caused by an earlier compilation error. The vlc.SlackBuild looks for a52dec support in a directory where the SlackBuild script compiled liba52 statically.
If you captured all the compilation console output you should look for the line that has "** a52 ...", the lines that follow are the process of compiling liba52. Look for issues there.

I never compiled on ARM so I have no idea what goes wrong there.

Eric

The problems seem to go deeper than only one dependency not compiling. I get a52 to compile and still have errors as well as trying to build without a52 support. I have looked into the building of ARMEDSlack and the build scripts used by Mr. Winter and it looks as if there is more to building on arm that is not covered with config options. I anticipate having a lot of research to do before I can accomplish vlc but if I want to move into arm using Slackware it will be well worth understanding it. Thanks again for looking into this.
BTW, I ran this same build script on my Slackware64 in VirtualBox and it ran flawlessly. On behalf of those of us in userland that benefit, thanks. We do appreciate your contributions to the Slackware experience.

Quote:

Originally Posted by ryerke (Post 4462580)

There really isn't more to building Slackware on ARM - my build environment is just geared to automation and is different than x86.
The README file in the 'source' directory explains how to use the build scripts in the armedslack tree.

Anyway, all you really do is set the CFLAGS to -march=armv5t (forget armv4 - there's no point running VLC on a machine with such a CPU (although you can still have low speed ARMv5 CPUs also)). Debian have the package, so it's definitley possible to build it.

Sorry for the delay in replying. I found that VLC builds nicely on ARMEDSlack with minimal options. This, of course, rules out the possibility of using Alien's build script, even with modifications for the arch. Since I am using a headless device, I don't need several of the options dealing with graphics. Many of those were the principal culprets breaking the build. My purpose for wanting VLC on this machine was mainly to live transcode for MediaTomb. It is yet to be determined if the processer is powerful enough to handle the load anyway.

Thanks so much for the help. I did indeed wonder about the build scripts and failed to understand the readme at first. This will help me greatly in the future building on ARM.
Bert

PS The initial install of ARMEDSlack on the GURUplug went flawlessly. Thank you for the work you have done to put this together.