PINE64
LibreELEC Krypton/Leia/Agile 64bit kernel 32bit libs - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: ROCK64 (https://forum.pine64.org/forumdisplay.php?fid=85)
+--- Forum: Linux on Rock64 (https://forum.pine64.org/forumdisplay.php?fid=88)
+--- Thread: LibreELEC Krypton/Leia/Agile 64bit kernel 32bit libs (/showthread.php?tid=5130)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20


RE: LibreELEC Krypton/Leia/Agile 64bit kernel 32bit libs - Raybuntu - 11-17-2017

(11-17-2017, 01:05 PM)Mrfixit2001 Wrote: @Raybuntu - when I try to compile I end up with "./libxml/encoding.h:29:19: fatal error: iconv.h: no such file or directory", #include <icon.v>
Obviously you can compile fine so I'm wondering if you have any tips or thoughts? I'm using cygwin64 on my win7 pc to compile. It runs for a good couple hours before it terminates.

Cygwin or any windows linux subsystem is not supported. Try to use either docker (there is a docker file) or s Ubuntu 16.04 Virtual maschine.


RE: LibreELEC Krypton/Leia/Agile 64bit kernel 32bit libs - Mrfixit2001 - 11-17-2017

@Raybuntu - I setup virtualbox and propped up ubuntu 16.04 VM. Gets much further but errors with:
Makefile:9: recipe for target 'release' failed
make: *** [release] Error 2
This occurs after: build.LibreELEC-ROCK64.arm-9.0-devel/binutils-2.29/gold/incremental.cc

If you have any advice I'd appreciate it.


RE: LibreELEC Krypton/Leia/Agile 64bit kernel 32bit libs - Raybuntu - 11-18-2017

Just restart the build process and pastebin more of the output otherwise there is no way to tell what's broken. Btw building from scratch LibreELEC master breaks from time to time.


RE: LibreELEC Krypton/Leia/Agile 64bit kernel 32bit libs - Raybuntu - 11-24-2017

https://github.com/Raybuntu/LibreELEC.tv/releases/tag/rb-leia17
This one could be a little bit more unstable.


RE: LibreELEC Krypton/Leia/Agile 64bit kernel 32bit libs - Luke - 11-25-2017

(11-24-2017, 08:11 AM)Raybuntu Wrote: https://github.com/Raybuntu/LibreELEC.tv/releases/tag/rb-leia17
This one could be a little bit more unstable.

For some reason I have sound crackling / stutteringĀ using SPDIF (audio POT) which were not present on the previous build.


RE: LibreELEC Krypton/Leia/Agile 64bit kernel 32bit libs - Mrfixit2001 - 11-25-2017

@Raybuntu - just wondering how difficult it would be to "downgrade" your source code back to the latest stable release of KODI? Seems like the newest build doesn't work with emulationstation or retroarch (both just close immediately and restart kodi). I'm attributing that to the newest kodi build being incompatible, but I welcome your feedback. I was wondering if it might be as easy as update the packages with the older kodi version numbers and recompiling? And do you think this would resolve the emulationstation and retroarch problem?


RE: LibreELEC Krypton/Leia/Agile 64bit kernel 32bit libs - Raybuntu - 11-25-2017

You can just drop the previous tar in the /storage/. update folder and reboot.


RE: LibreELEC Krypton/Leia/Agile 64bit kernel 32bit libs - dawnbandit - 11-25-2017

Will HDR support be possible eventually?


RE: LibreELEC Krypton/Leia/Agile 64bit kernel 32bit libs - Mrfixit2001 - 11-25-2017

Thanks for the quick reply. 3 questions... Are the issues in emulationstation and retroarch non existent in the previous version of KODI? And by using the previous tar don't I loose any of your updates to the rest of the packages and add ons? And which previous tar, considering there's no ROCK64 release for your krypton revision?


RE: LibreELEC Krypton/Leia/Agile 64bit kernel 32bit libs - Raybuntu - 11-27-2017

(11-25-2017, 05:38 PM)Mrfixit2001 Wrote: Thanks for the quick reply. 3 questions... Are the issues in emulationstation and retroarch non existent in the previous version of KODI? And by using the previous tar don't I loose any of your updates to the rest of the packages and add ons? And which previous tar, considering there's no ROCK64 release for your krypton revision?


Ahh ok you wanna use Krypton. No retroplayer is not supported in Krypton. You can loose addon updates respectively you could be forced to downgrade your addons.