Re: insmod - huawei E3372h kernel module
Zoran
> insmod /lib/modules/4.10.0/extra/huawei_cdc_ncm.ko > insmod: can't insert '/lib/modules/4.10.0/extra/huawei_cdc_ncm.ko': unknown symbol in module, or unknown parameter On my target (Pocket Bone): debian@arm:/lib/modules/5.8.18-bone24/kernel$ find . -name huawei_cdc_ncm* ./drivers/net/usb/huawei_cdc_ncm.ko.xz debian@arm:/lib/modules/5.8.18-bone24/kernel$ cd ./drivers/net/usb/ debian@arm:/lib/modules/5.8.18-bone24/kernel/drivers/net/sudo insmod huawei_cdc_ncm.ko.xz [ 6554.826591] huawei_cdc_ncm: Unknown symbol cdc_ncm_tx_fixup (err -2) [ 6554.833115] huawei_cdc_ncm: Unknown symbol cdc_ncm_bind_common (err -2) [ 6554.841745] huawei_cdc_ncm: Unknown symbol usb_cdc_wdm_register (err -2) [ 6554.849680] huawei_cdc_ncm: Unknown symbol cdc_ncm_unbind (err -2) [ 6554.857042] huawei_cdc_ncm: Unknown symbol cdc_ncm_rx_fixup (err -2) insmod: ERROR: could not insert module huawei_cdc_ncm.ko.xz: Unknown symbol in module debian@arm:/lib/modules/5.8.18-bone24/kernel/drivers/net/usb$ uname -a Linux arm 5.8.18-bone24 #1 PREEMPT Sun Dec 13 19:15:04 CET 2020 armv7l GNU/Linux debian@arm:/lib/modules/5.8.18-bone24/kernel/drivers/net/usb$ cat /etc/debian_version 10.7 debian@arm:/lib/modules/5.8.18-bone24/kernel/drivers/net/usb$ Good Luck! Zoran _______
On Fri, Jan 8, 2021 at 12:22 PM Zoltan Kerenyi Nagy <kerenyi.nagy.zoltan@...> wrote: No success :-(
|
|
Re: insmod - huawei E3372h kernel module
Zoltan Kerenyi Nagy
No success :-(
insmod /lib/modules/4.10.0/extra/huawei_cdc_ncm.ko insmod: can't insert '/lib/modules/4.10.0/extra/huawei_cdc_ncm.ko': unknown symbol in module, or unknown parameter -- Zolee
|
|
rebuild issues using sstate mirror
Markus Volk
Hi Folks,
i did some research on building a custom yocto image using gatesgarth branch. The testcase was building an image on one machine and rebuild it on another using sstate mirror. I encountered two issues witch i was able to fix in a way that may also be interesting upstream. The first error: | /home/flk/yocto/build/poky-3.2/hd51/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/gobject-introspection/1.64.1-r0/recipe-sysroot-native/usr/bin/bison: error while loading shared libraries: libreadline.so.7: cannot open shared object file: No such file or directory the solution for me was to add 'readline' to DEPENDS in bison_3.7.2.bb . configure log for bison-native changed from: checking for readline... no checking readline/readline.h usability... no checking readline/readline.h presence... no checking for readline/readline.h... no checking readline/history.h usability... no checking readline/history.h presence... no checking for readline/history.h... no to: checking for readline... yes checking how to link with libreadline... /home/flk/yocto/build/poky-3.2/hd51/tmp/work/x86_64-linux/bison-native/3.7.2-r0/recipe-sysroot-native/usr/lib/libreadline.so -Wl,-rpath -Wl,/home/flk/yocto/build/poky-3.2/hd51/tmp/work/x86_64-linux/bison-native/3.7.2-r0/recipe-sysroot-native/usr/lib checking readline/readline.h usability... yes checking readline/readline.h presence... yes checking for readline/readline.h... yes checking readline/history.h usability... yes checking readline/history.h presence... yes checking for readline/history.h... yes and the error disappeared The second error: ERROR: neutrino-image-1.0-r0 do_rootfs: Unable to update the package index files. Command '/home/flk/yocto/build/poky-3.2/hd60/tmp/work/hd60-oe-linux-gnueabi/neutrino-image/1.0-r0/recipe-sysroot-native/usr/bin/opkg --volatile-cache -f /home/flk/yocto/build/poky-3.2/hd60/tmp/work/hd60-oe-linux-gnueabi/neutrino-image/1.0-r0/opkg.conf -t /home/flk/yocto/build/poky-3.2/hd60/tmp/work/hd60-oe-linux-gnueabi/neutrino-image/1.0-r0/temp/ipktemp/ -o /home/flk/yocto/build/poky-3.2/hd60/tmp/work/hd60-oe-linux-gnueabi/neutrino-image/1.0-r0/rootfs --force_postinstall --prefer-arch-to-version update' returned 127: /home/flk/yocto/build/poky-3.2/hd60/tmp/work/hd60-oe-linux-gnueabi/neutrino-image/1.0-r0/recipe-sysroot-native/usr/bin/opkg: error while loading shared libraries: libcharset.so.1: cannot open shared object file: No such file or directory after some research why libiconv libs are being used (which i didn't have installed on the rebuild machine) i found this in libarchive: configure.ac and was able to avoid the error by including 'gettext' to the inherit line in libarchive_3.4.3.bb Kind regards
|
|
Quentin Schulz
On Fri, Jan 08, 2021 at 03:07:43AM -0800, Vijay Rakesh Munganda wrote:
On Fri, Jan 8, 2021 at 01:26 AM, Quentin Schulz wrote:If you go into ${WORKDIR} of your recipe (tmp/work/<arch>/<recipe name>),By changing to S = "${WORKDIR}/libopentok_linux_llvm_arm64" error got eliminated, thank you. what is the path to libopentok.*.so? Quentin
|
|
Vijay Rakesh Munganda
On Fri, Jan 8, 2021 at 01:26 AM, Quentin Schulz wrote:
Hi,By changing to S = "${WORKDIR}/libopentok_linux_llvm_arm64" error got eliminated, thank you. Now, how can I install the file under opentok_linux_llvm_arm64/lib/libopentok.so into the rootfs? I tried the below code but got an error as install: cannot stat 'lib/libopentok.so': No such file or directory. Thanks, Vijay Rakesh.
|
|
Vijay Rakesh Munganda
On Fri, Jan 8, 2021 at 01:28 AM, Paul Barker wrote:
I figured out URL is hyperlinked with another URL. When I use a hyperlinked URL it is getting copied and extracted into the working directory. Thanks.Hi Paul Barker,What I mean is, do you see the file Thanks, Vijay Rakesh.
|
|
Re: insmod - huawei E3372h kernel module
Zoltan Kerenyi Nagy
Hi,
I managed to bitbake with these: http://paste.ubuntu.com/p/4W2525MQDj/ http://paste.ubuntu.com/p/VT3zyhy7h2/ I'm very curious how it behaves on the hardware -- Zolee
|
|
Re: insmod - huawei E3372h kernel module
Zoltan Kerenyi Nagy
Hi,
Makefile: huawei_cdc_ncm-y := huawei_cdc_ncm.oobj-m += huawei_cdc_ncm.oKDIR ?= /lib/modules/`uname -r`/buildall:make -C $(KDIR) M=$(PWD) modulesclean:make -C $(KDIR) M=$(PWD) cleaninstall:cp *.ko /lib/modules/$(shell uname -r)/kernel/drivers/misc/depmod -aThis one doesnt work: DEBUG: Executing shell function do_compileNOTE: make -j 8 KERNEL_SRC=/home/kerenyiz/oe-core/build/tmp-glibc/work-shared/barix-ipam400/kernel-source KERNEL_PATH=/home/kerenyiz/oe-core/build/tmp-glibc/work-shared/barix-ipam400/kernel-source KERNEL_VERSION=4.10.0 CC=arm-oe-linux-gnueabi-gcc -fuse-ld=bfd LD=arm-oe-linux-gnueabi-ld.bfd AR=arm-oe-linux-gnueabi-ar O=/home/kerenyiz/oe-core/build/tmp-glibc/work-shared/barix-ipam400/kernel-build-artifacts KBUILD_EXTRA_SYMBOLS=ERROR: oe_runmake failedmake -C /lib/modules/`uname -r`/build M=/home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0 modulesmake[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule.make[1]: Entering directory '/usr/src/linux-headers-4.15.0-88-generic'make[2]: Entering directory '/home/kerenyiz/oe-core/build/tmp-glibc/work-shared/barix-ipam400/kernel-build-artifacts'make[3]: Circular /home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0/huawei_cdc_ncm.o <- /home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0/huawei_cdc_ncm.o dependency dropped.LD [M] /home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0/huawei_cdc_ncm.oarm-oe-linux-gnueabi-ld.bfd: no input files/usr/src/linux-headers-4.15.0-88-generic/scripts/Makefile.build:578: recipe for target '/home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0/huawei_cdc_ncm.o' failedmake[3]: *** [/home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0/huawei_cdc_ncm.o] Error 1/usr/src/linux-headers-4.15.0-88-generic/Makefile:1577: recipe for target '_module_/home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0' failedmake[2]: *** [_module_/home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0] Error 2make[2]: Leaving directory '/home/kerenyiz/oe-core/build/tmp-glibc/work-shared/barix-ipam400/kernel-build-artifacts'Makefile:146: recipe for target 'sub-make' failedmake[1]: *** [sub-make] Error 2make[1]: Leaving directory '/usr/src/linux-headers-4.15.0-88-generic'Makefile:25: recipe for target 'all' failedmake: *** [all] Error 2ERROR: F--Zolee
|
|
On Fri, 8 Jan 2021 at 09:20, Vijay Rakesh Munganda
<vijayrakeshmunganda@...> wrote: What I mean is, do you see the file "libopentok_linux_llvm_arm64-2.18.1.tgz" itself under ${WORKDIR}? i.e. has it been copied instead of extracted? Also, please quote the email you're replying to for the benefit of others on the mailing list. Replying inline like this is preferred. Thanks, -- Paul Barker Konsulko Group
|
|
Quentin Schulz
Hi,
On Fri, Jan 08, 2021 at 01:19:51AM -0800, Vijay Rakesh Munganda wrote: Hi Paul Barker,S = "${WORKDIR}/libopentok_linux_llvm_arm64" This is the root directory of your archive and should be used for `S` Cheers, Quentin
|
|
Vijay Rakesh Munganda
Hi Paul Barker,
No, ${WORKDIR}/tokbox directory is empty, it is not getting placed. I can only see it in the downloads directory. I'm Yocto Project Dunfell version. Thanks, Vijay Rakesh.
|
|
On Fri, 8 Jan 2021 at 08:49, Vijay Rakesh Munganda
<vijayrakeshmunganda@...> wrote: Does the .tgz file get placed in ${WORKDIR} without being extracted? Also, which Yocto Project version/branch are you using? Thanks, -- Paul Barker Konsulko Group
|
|
Re: How to select Linux kernel version?
Quentin Schulz
Hi Jupiter,
On Fri, Jan 08, 2021 at 02:03:47PM +1100, Jupiter wrote: Thanks Quentin, here are results:[...]So we can stop half guessing and help you can you give us the output of:bitbake -e virtual/kernel | grep -e "^PREFERRED_PROVIDER_"$ bitbake -e virtual/kernel | grep -e "^PREFERRED_PROVIDER_" PREFERRED_PROVIDER_virtual/kernel="linux-yocto"[...] Not sure this will fly nicely (the kernel headers being older than yourbitbake -e virtual/kernel | grep -e "^PREFERRED_VERSION_"$ bitbake -e virtual/kernel | grep -e "^PREFERRED_VERSION_" kernel). Otherwise ok. And here we have the winner :)bitbake -e virtual/kernel | grep -e "^OVERRIDES="$ bitbake -e virtual/kernel | grep -e "^OVERRIDES=" You don't have a 5.10 linux-yocto recipe so obviously bitbake can't compile it. Now, I don't know why 4.19 is taken and not 5.2. I quickly looked into both recipes and didn't find a DEFAULT_PREFERENCE (c.f. https://docs.yoctoproject.org/ref-manual/variables.html?highlight=preference#term-DEFAULT_PREFERENCE). So, can you tell us how you created your 5.10 recipe and where you put it (the filename, the path in the layer, is it in a new layer? if yes, did you add it to bblayers.conf? etc...). Quentin
|
|
Vijay Rakesh Munganda
Hi Zoran,
Thanks for the reply. The reason behind CMakeLists.txt does not appear is because tgz file is getting extracted into the source folder, it is empty when I checked. My recipe is unable to extract the tgz file which is download in the downloads directory. Do I need to write something specifically for extracting tgz file in the recipe? Thanks, Vijay Rakesh.
|
|
Zoran
Just maybe... This web pointer can help you!
https://stackoverflow.com/questions/46448682/cmake-error-the-source-does-not-appear-to-contain-cmakelists-txt/52068568 Zoran _______ On Fri, Jan 8, 2021 at 7:18 AM Vijay Rakesh Munganda <vijayrakeshmunganda@...> wrote:
|
|
Vijay Rakesh Munganda
Anyone, please suggest.
Thanks, Vijay Rakesh
|
|
Re: How to select Linux kernel version?
JH
Thanks Quentin, here are results:
So we can stop half guessing and help you can you give us the output of: bitbake -e virtual/kernel | grep -e "^PREFERRED_PROVIDER_"$ bitbake -e virtual/kernel | grep -e "^PREFERRED_PROVIDER_" PREFERRED_PROVIDER_console-tools="kbd" PREFERRED_PROVIDER_dbus-glib="dbus-glib" PREFERRED_PROVIDER_dbus-glib-native="dbus-glib-native" PREFERRED_PROVIDER_gdb="gdb" PREFERRED_PROVIDER_gdk-pixbuf="gdk-pixbuf" PREFERRED_PROVIDER_getopt="util-linux-getopt" PREFERRED_PROVIDER_gzip-native="pigz-native" PREFERRED_PROVIDER_libgcc="libgcc" PREFERRED_PROVIDER_linux-libc-headers="linux-libc-headers" PREFERRED_PROVIDER_ltp="ltp" PREFERRED_PROVIDER_matchbox-panel="matchbox-panel-2" PREFERRED_PROVIDER_nativesdk-libgcc="nativesdk-libgcc" PREFERRED_PROVIDER_nativesdk-linux-libc-headers="nativesdk-linux-libc-headers" PREFERRED_PROVIDER_nativesdk-mesa="nativesdk-mesa" PREFERRED_PROVIDER_nativesdk-openssl="nativesdk-openssl" PREFERRED_PROVIDER_nativesdk-opkg="nativesdk-opkg" PREFERRED_PROVIDER_nativesdk-pkgconfig="nativesdk-pkgconfig" PREFERRED_PROVIDER_openssl="openssl" PREFERRED_PROVIDER_openssl-native="openssl-native" PREFERRED_PROVIDER_opkg="opkg" PREFERRED_PROVIDER_opkg-native="opkg-native" PREFERRED_PROVIDER_pkgconfig="pkgconfig" PREFERRED_PROVIDER_pkgconfig-native="pkgconfig-native" PREFERRED_PROVIDER_udev="systemd" PREFERRED_PROVIDER_virtual/base-utils="busybox" PREFERRED_PROVIDER_virtual/egl="mesa" PREFERRED_PROVIDER_virtual/fakeroot-native="pseudo-native" PREFERRED_PROVIDER_virtual/gettext="gettext" PREFERRED_PROVIDER_virtual/i686-oe-linux-binutils="binutils-cross-i686" PREFERRED_PROVIDER_virtual/i686-oe-linux-compilerlibs="gcc-runtime" PREFERRED_PROVIDER_virtual/i686-oe-linux-g++="gcc-cross-i686" PREFERRED_PROVIDER_virtual/i686-oe-linux-gcc="gcc-cross-i686" PREFERRED_PROVIDER_virtual/kernel="linux-yocto" PREFERRED_PROVIDER_virtual/libc="glibc" PREFERRED_PROVIDER_virtual/libc-locale="glibc-locale" PREFERRED_PROVIDER_virtual/libgl="mesa" PREFERRED_PROVIDER_virtual/libgl-native="mesa-native" PREFERRED_PROVIDER_virtual/libgles1="mesa" PREFERRED_PROVIDER_virtual/libgles2="mesa" PREFERRED_PROVIDER_virtual/libiconv="glibc" PREFERRED_PROVIDER_virtual/libintl="glibc" PREFERRED_PROVIDER_virtual/libx11="libx11" PREFERRED_PROVIDER_virtual/make="make" PREFERRED_PROVIDER_virtual/make-native="make-native" PREFERRED_PROVIDER_virtual/mesa="mesa" PREFERRED_PROVIDER_virtual/nativesdk-libc="nativesdk-glibc" PREFERRED_PROVIDER_virtual/nativesdk-libgl="nativesdk-mesa" PREFERRED_PROVIDER_virtual/nativesdk-libiconv="nativesdk-glibc" PREFERRED_PROVIDER_virtual/nativesdk-libintl="nativesdk-glibc" PREFERRED_PROVIDER_virtual/update-alternatives="opkg-utils" PREFERRED_PROVIDER_virtual/update-alternatives-native="opkg-utils-native" PREFERRED_PROVIDER_virtual/x86_64-oesdk-linux-binutils-crosssdk="binutils-crosssdk-x86_64-oesdk-linux" PREFERRED_PROVIDER_virtual/x86_64-oesdk-linux-compilerlibs="nativesdk-gcc-runtime" PREFERRED_PROVIDER_virtual/x86_64-oesdk-linux-g++="gcc-crosssdk-x86_64-oesdk-linux" PREFERRED_PROVIDER_virtual/x86_64-oesdk-linux-gcc="gcc-crosssdk-x86_64-oesdk-linux" PREFERRED_PROVIDER_virtual/xserver="xserver-xorg" PREFERRED_PROVIDER_virtual/xserver-xf86="xserver-xorg" PREFERRED_PROVIDER_xf86-video-intel="xf86-video-intel" bitbake -e virtual/kernel | grep -e "^PREFERRED_VERSION_"$ bitbake -e virtual/kernel | grep -e "^PREFERRED_VERSION_" PREFERRED_VERSION_binutils="2.32%" PREFERRED_VERSION_binutils-cross-canadian-i686="2.32%" PREFERRED_VERSION_binutils-cross-i686="2.32%" PREFERRED_VERSION_binutils-crosssdk-x86_64-oesdk-linux="2.32%" PREFERRED_VERSION_binutils-native="2.32%" PREFERRED_VERSION_cross-localedef-native="2.30%" PREFERRED_VERSION_gcc="9.%" PREFERRED_VERSION_gcc-cross-canadian-i686="9.%" PREFERRED_VERSION_gcc-cross-i686="9.%" PREFERRED_VERSION_gcc-cross-initial-i686="9.%" PREFERRED_VERSION_gcc-crosssdk-initial-x86_64-oesdk-linux="9.%" PREFERRED_VERSION_gcc-crosssdk-x86_64-oesdk-linux="9.%" PREFERRED_VERSION_gcc-runtime="9.%" PREFERRED_VERSION_gcc-sanitizers="9.%" PREFERRED_VERSION_gdb="8.3%" PREFERRED_VERSION_gdb-cross-canadian-i686="8.3%" PREFERRED_VERSION_gdb-cross-i686="8.3%" PREFERRED_VERSION_glibc="2.30%" PREFERRED_VERSION_glibc-locale="2.30%" PREFERRED_VERSION_glibc-mtrace="2.30%" PREFERRED_VERSION_glibc-scripts="2.30%" PREFERRED_VERSION_go="1.12%" PREFERRED_VERSION_go-cross-canadian-i686="1.12%" PREFERRED_VERSION_go-cross-core2-32="1.12%" PREFERRED_VERSION_go-crosssdk-x86_64="1.12%" PREFERRED_VERSION_go-native="1.12%" PREFERRED_VERSION_go-runtime="1.12%" PREFERRED_VERSION_libgcc="9.%" PREFERRED_VERSION_libgcc-initial="9.%" PREFERRED_VERSION_libgfortran="9.%" PREFERRED_VERSION_linux-libc-headers="5.2%" PREFERRED_VERSION_linux-yocto="5.10.%" PREFERRED_VERSION_llvm="8.0.1" PREFERRED_VERSION_llvm-native="8.0.1" PREFERRED_VERSION_nativesdk-gcc="9.%" PREFERRED_VERSION_nativesdk-gcc-runtime="9.%" PREFERRED_VERSION_nativesdk-gcc-sanitizers="9.%" PREFERRED_VERSION_nativesdk-glibc="2.30%" PREFERRED_VERSION_nativesdk-go="1.12%" PREFERRED_VERSION_nativesdk-go-runtime="1.12%" PREFERRED_VERSION_nativesdk-libgcc="9.%" PREFERRED_VERSION_nativesdk-libgcc-initial="9.%" PREFERRED_VERSION_nativesdk-linux-libc-headers="5.2%" PREFERRED_VERSION_nativesdk-llvm="8.0.1" PREFERRED_VERSION_nativesdk-qemu="4.1%" PREFERRED_VERSION_qemu="4.1%" PREFERRED_VERSION_qemu-native="4.1%" PREFERRED_VERSION_virtual/i686-oe-linux-go="1.12%" PREFERRED_VERSION_wpa_supplicant="2.6" bitbake -e virtual/kernel | grep -e "^OVERRIDES="$ bitbake -e virtual/kernel | grep -e "^OVERRIDES=" OVERRIDES="linux:i686:pn-linux-yocto:x86:qemuall:qemux86:solar-distro:class-target:libc-glibc:forcevariable" bitbake-layers show-recipes linux-yocto linux-fslc$ bitbake-layers show-recipes linux-yocto linux-fslc NOTE: Starting bitbake server... Loading cache: 100% |############################################| Time: 0:00:00 Loaded 1473 entries from dependency cache. Parsing recipes: 100% |##########################################| Time: 0:00:02 Parsing of 922 .bb files complete (920 cached, 2 parsed). 1475 targets, 295 skipped, 0 masked, 0 errors. === Matching recipes: === linux-fslc: meta-freescale 5.1 (skipped) linux-yocto: meta 5.2.28+gitAUTOINC+dd6019025c_992280855e meta 4.19.87+gitAUTOINC+4f5d761316_b44ad1b1e7 $ cat local.conf ............ PREFERRED_PROVIDER_virtual/kernel="linux-yocto" PREFERRED_VERSION_linux-yocto = "5.10.%" ............. Thank you very much. Kind regards, - jupiter
|
|
Suggestions on improvements
Meh Mbeh Ida Delphine <idadelm@...>
Hello everyone, I'm trying to improve the Yocto Project's license tracing based on a proof-of concept implementation of linking sources with SPDX headers to output files by Richard at http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=rpurdie/license-experiments-osls. The code in package.bbclass creates a list of SPDX headers found for the sources that make up a given set of binaries that make up an individual package using debug symbols to map sources to the binaries. This is then compared with the license field of the given package containing those binaries. Due to some mismatches, warnings pop up during the build. Below are some few sample warnings and I'm aware of false positives; WARNING: glibc-2.32-r0 do_package: License for package nscd is {'GPL-2.0 WITH Linux-syscall-note'} vs GPLv2 & LGPLv2.1 WARNING: glibc-2.32-r0 do_package: License for package sln is {'GPL-2.0 WITH Linux-syscall-note'} vs GPLv2 & LGPLv2.1 WARNING: glibc-2.32-r0 do_package: License for package ldconfig is {'GPL-2.0 WITH Linux-syscall-note'} vs GPLv2 & LGPLv2.1 WARNING: glibc-2.32-r0 do_package: License for package glibc is {'GPL-2.0 WITH Linux-syscall-note'} vs GPLv2 & LGPLv2.1 WARNING: glibc-2.32-r0 do_package: License for package glibc-staticdev is {'GPL-2.0 WITH Linux-syscall-note'} vs GPLv2 & LGPLv2.1 WARNING: libcap-ng-0.8-r0 do_package: License for package libcap-ng is {'GPL-2.0 WITH Linux-syscall-note'} vs GPLv2+ & LGPLv2.1+ WARNING: libtirpc-1.2.6-r0 do_package: License for package libtirpc is {'GPL-2.0 WITH Linux-syscall-note'} vs BSD-3-Clause WARNING: ptest-runner-2.4.0+gitAUTOINC+834670317b-r0 do_package: License for package ptest-runner is {'GPL-2.0-or-later'} vs GPLv2+ WARNING: libcap-2.44-r0 do_package: License for package libcap is {'GPL-2.0 WITH Linux-syscall-note'} vs BSD | GPLv2 WARNING: libcap-2.44-r0 do_package: License for package libcap-staticdev is {'GPL-2.0 WITH Linux-syscall-note'} vs BSD | GPLv2 WARNING: openssl-1.1.1h-r0 do_package: License for package openssl-engines is {'GPL-2.0 WITH Linux-syscall-note', 'GPL-2.0+ WITH Linux-syscall-note'} vs openssl Any suggestions on improvements I can make to this functionality? Cheers, Ida.
|
|
Re: [meta-tensorflow][PATCH 8/25] tensorflow-estimator: 1.13 -> 2.4
On 2021-01-07 1:47 p.m., Belisko Marek wrote:
Hi Marek,Marek,Yes this comes from master branch. Is it: A) Comes from master and is a problem on dunfell or B) it is reproducible on the master branch? Given that you said: I'm getting issue when building tensorflow-estimator (I add smallI suspect it's A only. Right? What are your small changes. Hongxu may take a quick look but we generally can't afford to investigate all combinations of recipe/branchs as I'm sure you can appreciate. If you can reproduce the error on master without or even with your changes then that's a different story. Good luck and Happy New Year! -- # Randy MacLeod # Wind River Linux
|
|
Re: [meta-tensorflow][PATCH 8/25] tensorflow-estimator: 1.13 -> 2.4
Marek Belisko
HI Randy,
On Thu, Jan 7, 2021 at 6:51 PM Randy MacLeod <randy.macleod@...> wrote: Yes this comes from master branch. BR, marek
-- as simple and primitive as possible ------------------------------------------------- Marek Belisko - OPEN-NANDRA Freelance Developer Ruska Nova Ves 219 | Presov, 08005 Slovak Republic Tel: +421 915 052 184 skype: marekwhite twitter: #opennandra web: http://open-nandra.com
|
|