Cubox: cryptodev support, marvell-ipp and xbmc

[aldrik]

No description provided.

[kmihelich]

I can tell you now the openssl-cryptodev package will fail to build on the v7h builders in the farm with that pkgbuild. Give me a little bit to figure out what to do about that.

[pepedog]

When are you going to finish this off, n3on?
https://aur.archlinux.org/packages/marvell-ipp/

[kmihelich]

Technically, ARM packages do not belong in the AUR.

[aldrik]

pepedog, I've already got marvell-ipp compiling libmiscgen.so. Please let me know if there's additional changes needed.

kmihelich, I didn't added it here as there's nothing depending on it. Such as: https://aur.archlinux.org/packages/marvell-xbmc-git/ (not sure about the package name). If either would be excepted I'll happily make pull request(s).

[pepedog]

That is what I meant, I saw it built the lib. Goes in alarm

[kmihelich]

For xbmc, to follow what we already have, I'd say name it xbmc-cubox-git seeing as there's really just the Cubox that is using it.

For the openssl-cryptodev package, you should do what you did in the libcec package. Makedepend on linux-headers-cubox, and use the same _kernel_release setup to point it to the correct kernel headers directory. That should allow it to build fine.

[aldrik]

Bump — guess I need to add a comment to let you guys know about the updated commits? I made the requested changes.

[kmihelich]

Yeah, github doesn't send out emails for commits, just comments. I'll take a look at things tonight.

[kmihelich]

In xbmc-cubox-git:

patching file configure.in
Hunk #1 FAILED at 1150.
1 out of 1 hunk FAILED -- saving rejects to file configure.in.rej
�[1m�[31m==> ERROR:�[m��[1m A failure occurred in build().�[m�
�[1m Aborting...�[m�

If you were building against a specific location of the xbmc git, you should add it into the PKGBUILD so that it gets that source and the build succeeds. Or the patch needs to be fixed.