The AUR package "just" does this
https://aur.archlinux.org/packages/ri/rivendell/PKGBUILD
download files, patch them, runs configure and make... but maybe
doesn't fit arch linux arm paths. Not sure.
Trying a straight ./configure -> make gives
make[1]: Entering directory `/home/alessio/rivendell-2.3.0/lib'
CXX export_bmiemr.lo
In file included from ./rddb.h:30:0,
from export_bmiemr.cpp:24:
./rdconfig.h:89:3: error: ���uid_t��� does not name a type
./rdconfig.h:90:3: error: ���gid_t��� does not name a type
./rdconfig.h:134:3: error: ���uid_t��� does not name a type
./rdconfig.h:135:3: error: ���gid_t��� does not name a type
make[1]: *** [export_bmiemr.lo] Error 1
But this is probably why there are patches... I am not good on building stuff...
...
2013/1/27 James Harrison <[email protected]>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> No idea on the AUR package, however thought I'd chime in on one thing
> - - the h264 decoding and 1080p display output is done by on the on-die
> GPU, which is not a general purpose compute chip. There is a CPU which
> is a 'mere' 700MHz ARM chip which may or may not run Rivendell
> smoothly. My bet would be on 'probably not smoothly enough for
> glitch-free audio'.
>
> The problem with invalid socket suggests that the ripcd daemon isn't
> able to write to the socket it wants to. I'm not sure what path it
> uses or if it's a network socket, but something to look at perhaps.
>
> Cheers,
> James Harrison
>
> On 27/01/2013 17:01, Alessio Elmi wrote:
>> Hi all, I remember someone tried using Rivendell on Raspbery Pi
>> using Debian (wheezy) image... Results weren't so good because of
>> the weak cpu on board.
>>
>> Something which is supposed to play smoothly a 1080p H.264 movie
>> should run Rivendell without a problem..
>>
>> I thought Arch Linux (with simple LXDE or razorqt) could give
>> better results so I tried to compile everything...
>>
>> Well I first tried with AUR package provided by Sebastien Leblanc,
>> with a small change on PKGBUILD. There are problems, like always.
>> Two main things: - QT libraries are installed in /opt/qt/.. and
>> this probably breaks something around... - (when I manually export
>> QT) it can't start Rivendell daemons... If I manually start "caed"
>> no problem... with "ripcd" I get "qsocketdevice::writeblock:
>> invalid socket" error message..
>>
>> Any idea guys?
>>
>> Alessio _______________________________________________
>> Rivendell-dev mailing list [email protected]
>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
>>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (MingW32)
>
> iEYEARECAAYFAlEFYysACgkQ22kkGnnJQAyR4QCeKeqQIGAIEeUK9kajsYbdOCUd
> 7McAnig1Q1LUJzes3etLQqp1fPfaqRzY
> =S/7j
> -----END PGP SIGNATURE-----
> _______________________________________________
> Rivendell-dev mailing list
> [email protected]
> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
