Posts by heitbaum

    Your probably reading too much into it. The build system runs many workflows and then many jobs within those workflows. We have been doing extra LE12 builds recently which will push out or cancel other builds. When a workflow runs - it runs 2 jobs at a time (in random order for the target architectures) and will pick the hash at the time of the job kick off - not the workflow kickoff.

    Whilst the job is scheduled nightly - it doesn’t mean there will always be a nightly.


    You can always check the scheduler for LE13 builds at https://github.com/LibreELEC/acti…/build-LE13.yml
    Or in total at https://github.com/LibreELEC/actions/actions

    may help the crystal ball be less cloudy.

    You can check the inner workings of the CI/CD environment here. https://github.com/LibreELEC/actions/actions builds of LE12 and LE13 take 18 hours each, and addons take 10-12 hours each. Builds only get kicked off if there have been changes in the last 24 hours. Workflows can only be in the queue for 24 hours. Priority is given to binary addons when required.

    So when only LE12 or LE13 are getting changes, you will see images and addons updated every 28-30 hours, but when changes are occurring on both LE12 and LE13 - you will see a 60 hour cycle.

    Workflows are cancelled automatically when passing 24 hours. Workflows (addons / images) are also cancelled when they won’t actually make change - eg addon update doesn’t need images rebuilt - because they were the same.

    Hope that answers your questions.

    This bit I can’t help with, as I haven’t used iscsi.

    👍 Glad you got your build working.

    I update gcc and g++ to version 14.1.0.

    I tried lunch build (with fix and without fix(loading new git) ) , but not success.
    Now error cmake (013/313)

    I installed cmake, but not success.

    We build our own copy of cmake (it is failing for some reason)

    Details will be in the build.LibreELEC-Generic.x86_64-13.0-devel/.threads/logs/13.log log file


    1. But first go back to “your working machine” before you added gcc14. Ubuntu doesn’t have a gcc-14

    2. Check the build. Run something like the following commands

    cd /home/tod

    mv LibreELEC.tv old

    git clone https://github.com/LibreELEC/LibreELEC.tv.git

    cd LibreELEC.tv

    # wget … as above

    # git am … as above

    # we are not going to build open-iscsi yet

    # let’s test you build environment

    make image

    # share your success/logs

    # move on to scripts/build open-iscsi


    Booting an image with iscsi may not/probably won’t work (or you might need to do some/a lot of work) we haven’t tested an iscsi build for a long time.

    Thx.
    On the computer where I am building libreelec (x64 Ubuntu 22.04 - 64bit) is installed. At the moment I am compiling gcc-14, because... This fix, as I understand it, requires version 14. The terminal showed this: Application: open-iscsi: fix build with gcc-14.
    I try it and write here.

    You won’t need gcc-14 to do the build (it will cause other issues), it looks like it has made your build host unstable.

    The patches themselves are for the LE build system (as we compile a copy of gcc during the build)

    The LE build will run with no problems on a “clean Ubuntu 22.04 or 24.04” system.

    If in your LibreELEC.tv directory you do the following, that patches to fix the compile error will be added.


    Code
    wget https://github.com/LibreELEC/LibreELEC.tv/pull/9163.patch
    git am 9163.patch

    # or the following if you are not using a git clone

    Code
    patch -p1 < 9163.patch

    I have done a test using noble (with host gcc 14) and needed the 3 patches in my gcc-14 branch (as I had expected) I needed to remove openjdk-21-jre-headless and use openjdk-17-jre-headless

    Commits · heitbaum/LibreELEC.tv
    Just enough OS for KODI. Contribute to heitbaum/LibreELEC.tv development by creating an account on GitHub.
    github.com

    Then did scripts/build kodi

    The build was successful

    Note: le11 11.0.6 was built with the jammy docker image in our GitHub Actions.

    duncang92 we are trying to test this ssl issue, and can’t reproduce it yet.


    Can your please confirm the password to your mariadb matches between the advancedsettings.xml and the mariadb. The password won’t be “kodi”. Please don’t share your password here - but it should be the ddddd line.

    please also test the following line - it should let you in to the database.
    # mariadb -h 192.168.68.51 --skip-ssl-verify-server-cert -u kodi -p