Posts by heitbaum

  • FTPS broken in LE12

    I can’t see anything in the log either. Suggest checking in on the Kodi forum for the “missing” file / folders now that we have ruled out curl itself (that doesn’t mean it still might not be curl - but it will be the api of curl)

  • FTPS broken in LE12

    I would suggest testing if curl or Kodi/curl api is the issue. Kodi Piers (LE13) is in development presently with curl 8.13.0. If there is an issue it would be the right time to get it fixed at the source.

    From LE - something like -

    curl -k --user myusername:mypassword ftps://ftpserver.mine

    and check that it is showing you the files you expect, they are accessible ….
    - and why / what are the missing files?
    What is the common pattern? E.g. Is it path length…. Is it special characters?

    if a curl issue, then needs to be raised with the curl team (they release approximately every 2 months)

    If a Kodi issue then will need to be raised on the Kodi forum with a reproducible case.

    but first best share debug logs will be required to analyze further with the current LE13 nightlies.

    Also the results of the “locally executed curl”

  • Source archive is never downloaded for custom package - why?

    Typo? PGK_URL

  • [x86-64] ZFS Support

    Quote from dikov

    Heitbaum,

    Thank you for the suggestion. This indeed helped to install zfs kernel modules along with others, so when I boot it i have all modules in place, but zfs userspace tools (zpool and )

    How to add them?

    the command seems to install all sorts of things. But you will need to trial and error find the right install command to get the files you want. Otherwise saferemove the files. Otherwise cp is an option.
    make install DESTDIR=${INSTALL}

    The below will help you work out what is going to end up in the image.
    find build.LibreELEC-Generic.x86_64-13.0-devel/install_pkg/zfs-2.3.0/

  • [x86-64] ZFS Support

    That is because it is building in the builddir for nano. Whereas zfs is building in the PKGDIR. Builddir is the usual for LE packages.

  • [x86-64] ZFS Support

    No need to declare variables before hand. I don’t know what they will do. Just a scripts/build zfs to build the zfs.


    Simple makeinstall_target is all that is necessary.

    Code
    makeinstall_target() {
  mkdir -p ${INSTALL}/$(get_full_module_dir)/fs/${PKG_NAME}
    cp module/*.ko ${INSTALL}/$(get_full_module_dir)/fs/${PKG_NAME}
}


  • [x86-64] ZFS Support

    Configure is doing strange stuff and not using the target compiler.

    build.LibreELEC-Generic.x86_64-13.0-devel/build/zfs-2.3.0/build/kernel_fpu_license/build.log
    make: Entering directory '/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-13.0-devel/build/linux-6.12.15'
    warning: the compiler differs from the one used to build the kernel
    The kernel was built by: x86_64-libreelec-linux-gnu-gcc-15.0.1 (GCC) 15.0.1 20250223 (experimental)
    You are using: gcc (Ubuntu 14.2.0-4ubuntu2~24.04) 14.2.0
    MODPOST /var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-13.0-devel/build/zfs-2.3.0/build/kernel_fpu_license
    /Module.symvers
    ERROR: modpost: GPL-incompatible module kernel_fpu_license.ko uses GPL-only symbol 'kernel_fpu_begin_mask'
    ERROR: modpost: GPL-incompatible module kernel_fpu_license.ko uses GPL-only symbol 'kernel_fpu_end'

    ==

    this will get you quite a bit further. It is not complete or fully working on the make.