01:06 <fuxxy> I'm stuck again. Build image fails, first error is "libcec-2fc92b5/src/libcec/env.h:93:86: error: stray '@' in program" - full error is http://paste.debian.net/1166562/ - I'm thinking it's related to me attempting to compile a commit version instead of a release. Would this be a LibCEC issue, or an issue with the buildtools?

02:53 <buzzmarshall> i am not familiar with that distro but if theres any patches in your package try rem

02:53 <buzzmarshall> them out

02:53 <buzzmarshall> and see if it will build the package

02:55 <buzzmarshall> the other thing i would do if this is the 1st time build would be to check things overall to see if the whole project builds

02:56 <buzzmarshall> is to turn off cec in the options file and see if the whole build completes, that way you'll know where to focus your efforts as you'll no the toolchain and support is good and the issue is confined to cec

02:57 <buzzmarshall> between all the old builds i seemed to always have some grief with cec in one of the distros or the other

03:08 <ponyofdeath> hi guys getting this for a 10bit video on pi4 https://bpa.st/UALA any ideas?

03:09 <ponyofdeath> and then my input dies

03:09 <ponyofdeath> i have to reboot to get kodi back

03:52 <fuxxy> buzzmarshall, finally found it. I restarted the build from scratch. I was attempting to upgrade libcec to the commit where the issue was fixed upstream, but it's WAAAY newer than what's in the repo. I'll probably just fork libcec at that commit and apply the patch to my fork until I have time for a proper merge.

03:56 <buzzmarshall> glad to see you got past that... i think the cec has the p8-platform as a dependency so the newer versions probaby require the newer toolchain

03:57 <buzzmarshall> tho you may be able to regress them backwards maybe to the toolchain your building against

03:58 <buzzmarshall> restarting was something else i meant to mention as i now a lot of times on the older build systems a restart seemed to get you past some errors

03:58 <buzzmarshall> i suspect its because of the order somethings are built in and i don't think the parallel build system was quite right at that point in time

04:17 <fuxxy> buzzmarshall, a lot of my issue is that I'm a novice at this stuff. I have the drive, just not the fundamental understanding of how all these packages are interdependant, as well as the build environment itself. I can't tell the difference between a dependency for the build environment vs a dependency for the final build. I'm slowly figuring it out, but that's what's making this drag out so long

04:22 <fuxxy> since I restarted the build, I decided to throw 12 cores with 4 threads each at it. TAKE THAT

04:26 <buzzmarshall> haha

07:56 <r0bert> mornin' all

07:57 <r0bert> i am using latest LE on an rpi4

07:57 <r0bert> i want to watch youtube-videos in 1080p and so far only had 720p

07:57 <r0bert> i followed the steps in this thread: https://forum.kodi.tv/showthread.php?tid=335356

07:58 <r0bert> getting 1080p now, however video is annoyingly slow

07:58 <r0bert> (will also occasionally jump to get back to sound)

07:58 <r0bert> what am i doing wrong? is there another way to configure the yt-addon properly to show 1080p?

08:43 <rdorsch> Thanks, lrusak. I assume the kodi-100.90-imx-quirk-plane-usage.patch does not work anymore due to the upgrade to mesa 20.2

08:44 <rdorsch> Do you expect that it is still needed?

09:16 <rdorsch> Looking at the patch itself: (m_module->name == "imx-drm" .... --- I am not an expert C programmer, but I would have expected strcmp(m_module,"imx-drm") .

09:16 <rdorsch> Looking at the patch itself: (m_module == "imx-drm" .... --- I am not an expert C programmer, but I would have expected strcmp(m_module,"imx-drm") .

09:21 <rdorsch> A, mesa is c++, so the == is a string relational operator.

09:22 <rdorsch> Where was the m_module defined?

13:51 <fuxxy> build.OpenPHT-Embedded-Generic.x86_64-8.2-devel/toolchain/x86_64-libreelec-linux-gnu/sysroot/usr/bin/python2.7: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory

14:16 <lrusak> rdorsch, m_module was removed in Kodi

14:28 <fuxxy> is there a way to chroot into the build environment?

14:49 <fuxxy> libpython2.7.so.1.0 exists at ./toolchain/x86_64-libreelec-linux-gnu/sysroot/usr/lib/ , not sure where exactly plexht is looking

15:05 <fuxxy> Here's a simple one - Where does packages/<pkgname>/package.mk get its variables from? If a package references $VARIABLE, where is that provided ?

15:56 <chewitt> look at the scripts in the functions folder

16:22 <fuxxy> ugh, disabled CEC everwhere I can, and plexht-1.9 *insists* on looking for the libs.

16:33 <fuxxy> Ahh, there it is. Even though the project can be created without CEC support, it's still listed as a dependancy in CMakeLists.txt

16:52 <fuxxy> chewitt, plexht-1.9 is pulled from this custom image I'm using. if a PKG_URL is not listed for plexht-1.9/package.mk, how is the build environment still able to pull the git repo? (I've forked the plexht-1.9 tree, I want to use my personal git)

16:56 <fuxxy> I'm assuming PKG_SITE is used, (which is currently http://www.openpht.tv), however that website is blank. If I'm right, openpht.tv must be using some http tricks to forward git requests to github

18:48 <rdorsch> lrusak, so you know if there is a replacement, which could be used instead?

21:53 <fuxxy> I know it can get complicated, but what should I expect in the process of installing updated libcec on an 8.2 source?