piotrasd tried everything with syslinux and he couldn't get it booting. Maybe something is missing in kernel too. If anyone has any direct tips let us know.
Maybe I didn't write correctly before. Syslinux did boot and kernel starts loading. But then only dark screen.
Last time we check syslinux didn't work. Only grub (and probably others).
To see more data when system boots you need to change console_arg line in uEnv.txt file on first partition on the sd card.
You can try to remove ccache folder, clean openssl package and build it again. For me it builds so don't know what it could be.
So i would have to fork the entire repo, isn't it?
You can only change your local copy.
You need to change version.
But sometimes you need to bump other related packages too.
git pull again and build - kodi package was updated yesterday.
When you are building package for host you will see linux-x86_64 because you are building on 64 bit system.
When building for target you will see linux-armv4.
This is all good 
Of course it could be with libreelec (more than 2 years passed!). But like I wrote cec works for others.
Than blame Samsung because they broke even more with latest updates.
But cec works in general.
Already fixed in repository.
Start with 8.0.0 found in LibreELEC.USB-SD.Creator or manually download and update (update works also with img.gz).
LibreELEC-imx6.arm-8.0.0.tar
LibreELEC-imx6.arm-8.0.0.img.gz
I also have Samsung TV and CEC works fine. But sometimes I need to search for devices on TV or at least switch to livetv and then back to hdmi.
Only buffering problem I saw (had/have) is when NAS is sleeping and needs to wake up.
I have never had the result I want from any of the in-house usb/sd creators.
Then I think you are in minority.
The only reason for such behaviour is refreshing USB drives which happens every 1.5 seconds when app has a focus. But others didn't have problems with this.
I just build master successfully. Not sure why it happens for you: because of Debian or because it is 32 bit system.
And if some files are used from /usr/include path then build process should be terminated because of this. Wondering why didn't kick in in your case.
Can you try to use 64 bit system?
Update: Would be possible to give me ssh access to this machine?
booted the cubox, and got no boot. red light is flicking constantly.
This means the system didn't even boot correctly anymore. Wondering why...
Ouch, this is the problem:/usr/include/stdlib.h. Let me rebuild and see if I have same issue.
What host system you are using?
Could be related to this: thread-3462.html
There is no solution yet.
