Failed to build chromium-vaapi
azhuchkov opened this issue · 10 comments
Got a problem about absence of libffi.so
during build.
Workaround (command to run): pacman -Syyuu --noconfirm && /build-aur chromium-vaapi
Hi, that's a strange workaround, could it be that you simply didn't pull the image before trying to build a package?
Gotcha. If you are building the image yourself, then you must ensure you pull the base image before building, to ensure the base image is updated - in this case it's defined here:
docker-arch-build-aur/Dockerfile
Line 1 in 3325f94
So docker pull archlinux/base:latest
and then build your image.
To take care of this, my image is being built daily by Travis, to make sure its dependencies are always up-to-date.
This is what I have:
$ docker image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
maximbaz/arch-build-aur latest 412e91ee94c9 5 hours ago 893MB
archlinux latest 9651b9e35f39 2 weeks ago 412MB
archlinux/base latest 345c9418cf48 3 weeks ago 502MB
...
I suppose it's the latest version which was pulled automatically during building your image.
Also I tried pulling image instead of building it - the result was the same.
docker build
doesn't pull updates to dependencies (it pulls them once only if they are entirely missing from your system), so you can see that archlinux/base is 3 weeks old, probably because 3 weeks ago you tried to build this image for the first time?
I have never used Arch inside docker. And didn't used docker for months. And I tried to build chromium-vaapi from 2 different machines, and 1 of them was fresh cloud server.
Ha, the base image itself stopped being update, https://hub.docker.com/r/archlinux/base/tags says it wasnt updated for 24 days! In that case sure, lets take your suggestion 👍
Should be fixed with f9d7787, thank you very much for letting me know about this problem!
Thanks for the image that allows to easily build heavy packages on dedicated hardware! I suppose it saved me many hours of CPU time.