Date   

Re: insmod - huawei E3372h kernel module

Zoltan Kerenyi Nagy
 

Intrestingly modprobe gives me a different error than insmod:
To me this means that it's gonna be a Yocto issue during bitbake.
My testing kernel module (hello word) bitbakes, and can be loaded and unloaded on the hardware
root@barix-ipam400:~# modprobe /lib/modules/4.10.0/extra/cdc-ncm.ko       
modprobe: module /lib/modules/4.10.0/extra/cdc-ncm.ko not found in modules.dep
root@barix-ipam400:~#
root@barix-ipam400:~# modprobe /lib/modules/4.10.0/extra/cdc-wdm.ko
modprobe: module /lib/modules/4.10.0/extra/cdc-wdm.ko not found in modules.dep
root@barix-ipam400:~#
root@barix-ipam400:~# modprobe /lib/modules/4.10.0/extra/h         
hello.ko           huawei_cdc_ncm.ko 
root@barix-ipam400:~# modprobe /lib/modules/4.10.0/extra/huawei_cdc_ncm.ko
modprobe: module /lib/modules/4.10.0/extra/huawei_cdc_ncm.ko not found in modules.dep
root@barix-ipam400:~#


--
Zolee


remove particular device from QB_OPT_APPEND: per-word manner

Sergey Ivanov <icegood1980@...>
 

Hi there.

I'm working with arm64 target and i want to take control on usb buses on it.
What i'm trying to do is tro remove both bus and hid devices on it via
QB_OPT_APPEND_remove = " -show-cursor -device qemu-xhci -device usb-tablet -device usb-kbd "

Of course, it doesn't work properly since it removes ALL occurrences of each word above. In particular, i had "-device VGA,edid=on" that i wanted to stay.
Instead, i obtained "VGA,edid=on" that lead to boot error. OK, it is clear. I also tried smth. like

QB_OPT_APPEND_remove = " -show-cursor '-device qemu-xhci' '-device usb-tablet' '-device usb-kbd -device' "

however nothing was removed here. Can i workaround given issue under Zeus?
--
Kind regards,
Sergey Ivanov


Re: Unable to add pre compiled library #yocto

Quentin Schulz
 

Hi VR,

On Tue, Jan 12, 2021 at 07:57:46PM +0530, Vijay Rakesh Munganda wrote:
Hi Raj,

I had downloaded complete meta-clang and ran bitbake then I got an error message as layer is not compatible with dunfell version. Then I had downloaded libcxx recipe and added into the build, but do_compile doesn’t show any progress, even after two hours at shows 16%. At this point RAM usage is 72% and CPU is 43%. I’m not sure whether this is related to memory resource or any other.
I told you on StackOverflow to checkout the dunfell branch of
meta-clang. Do that, and recompile again instead of cherry-picking
recipes, classes, patches and whatnot.
Once you've something that works, you can experiment with cherry-picking
if you want.

Cheers,
Quentin


Re: Unable to add pre compiled library #yocto

Vijay Rakesh Munganda
 

Hi Raj,

I had downloaded complete meta-clang and ran bitbake then I got an error message as layer is not compatible with dunfell version. Then I had downloaded libcxx recipe and added into the build, but do_compile doesn’t show any progress, even after two hours at shows 16%. At this point RAM usage is 72% and CPU is 43%. I’m not sure whether this is related to memory resource or any other.

Thanks & Regards,
VR

On 12-Jan-2021, at 14:38, Khem Raj <raj.khem@gmail.com> wrote:

On Mon, Jan 11, 2021 at 11:46 PM Vijay Rakesh Munganda
<vijayrakeshmunganda@gmail.com> wrote:
Hi,
I'm trying to install a pre-compiled library, but I got an error as follows. I had tried to add libcxx from meta-clang, but it doesn't compatible with Yocto dunfell version. Is there another way to avoid error?
it seems to need llvm C++ runtime and using meta-clang/libcxx is the
right way to go about it. What errors do you run into ?

ERROR: tokbox-2.18.1-r0 do_package_qa: QA Issue: /usr/lib/libopentok.so contained in package tokbox requires libc++.so.1()(64bit), but no providers found in RDEPENDS_tokbox? [file-rdeps]
ERROR: tokbox-2.18.1-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.
Thanks,
VR.


Re: Unable to add pre compiled library #yocto

Khem Raj
 

On Mon, Jan 11, 2021 at 11:46 PM Vijay Rakesh Munganda
<vijayrakeshmunganda@gmail.com> wrote:

Hi,

I'm trying to install a pre-compiled library, but I got an error as follows. I had tried to add libcxx from meta-clang, but it doesn't compatible with Yocto dunfell version. Is there another way to avoid error?
it seems to need llvm C++ runtime and using meta-clang/libcxx is the
right way to go about it. What errors do you run into ?

ERROR: tokbox-2.18.1-r0 do_package_qa: QA Issue: /usr/lib/libopentok.so contained in package tokbox requires libc++.so.1()(64bit), but no providers found in RDEPENDS_tokbox? [file-rdeps]
ERROR: tokbox-2.18.1-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.

Thanks,
VR.


Unable to add pre compiled library #yocto

Vijay Rakesh Munganda
 

Hi,

I'm trying to install a pre-compiled library, but I got an error as follows. I had tried to add libcxx from meta-clang, but it doesn't compatible with Yocto dunfell version. Is there another way to avoid error?

ERROR: tokbox-2.18.1-r0 do_package_qa: QA Issue: /usr/lib/libopentok.so contained in package tokbox requires libc++.so.1()(64bit), but no providers found in RDEPENDS_tokbox? [file-rdeps]
ERROR: tokbox-2.18.1-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.
Thanks,
VR.


Re: BITBAKE HANGS

U RAVI KUMAR <uppadaravi2511@...>
 

Hello Davis,

              I will try using 16 GB ram. Thank you very much for your response.
Thanks,
ravi uppada.

On Mon, Jan 11, 2021 at 11:18 PM Davis, Michael <michael.davis@...> wrote:

QTWebengine needs a considerable amount of RAM to compile and link relative to the rest of Yocto.

Normally around 12-16GB.  Less than that and the system tends to hang.

 

 

 

From: yocto@... <yocto@...> On Behalf Of U RAVI KUMAR via lists.yoctoproject.org
Sent: Monday, January 11, 2021 11:25 AM
To: yocto@...
Subject: [yocto] BITBAKE HANGS

 

hi guys,

 

 I have encountered with a problem.I have built a custom linux for raspberrypi and included meta-openembedded,meta-raspberrypi,meta-qt5,meta-python2 layers and compiled on the bitbake. it is working fine.

I have added recipe "qtwebengine" , here i have encountered an issue i.e the system hangs. only while compiling qtwebengine system hangs.Can anyone suggest me the solution.So that i canovercome and proceed fiurther..

 

Thanks and regards,

ravikumar



CONFIDENTIALITY NOTICE:

This e-mail transmission and any documents, files or previous e-mail messages attached to it may contain information that is confidential, protected by the attorney/client or other privileges, and may constitute non-public information. It is intended to be conveyed only to the designated recipient(s) named above.

Any unauthorized use, reproduction, forwarding, distribution or other dissemination of this transmission is strictly prohibited and may be unlawful. If you are not an intended recipient of this email transmission, please notify the sender by return e-mail and permanently delete any record of this transmission. Your cooperation is appreciated. To find out more Click Here.


M+ & H bugs with Milestone Movements WW02

Stephen Jolley
 

All,

YP M+ or high bugs which moved to a new milestone in WW02 are listed below:

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

Medium+

13919

Multi License GPLv3 -lic cannot be installed into the image because it has incompatible license

randy.macleod@...

idadelm@...

3.3 M1

3.3 M2

 

14077

devtool doesn't handle server failing to startup gracefully

randy.macleod@...

stacygaikovaia@...

3.3 M1

3.3 M2

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Enhancements/Bugs closed WW02!

Stephen Jolley
 

All,

The below were the owners of enhancements or bugs closed during the last week!

Who

Count

richard.purdie@...

5

randy.macleod@...

1

ross@...

1

chee.yang.lee@...

1

Grand Total

8

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Current high bug count owners for Yocto Project 3.3

Stephen Jolley
 

All,

Below is the list as of top 50 bug owners as of the end of WW02 of who have open medium or higher bugs and enhancements against YP 3.3.   There are 76 possible work days left until the final release candidates for YP 3.3 needs to be released.

Who

Count

richard.purdie@...

35

ross@...

27

david.reyna@...

21

bluelightning@...

19

bruce.ashfield@...

14

timothy.t.orling@...

12

JPEWhacker@...

11

mark.morton@...

11

kai.kang@...

10

akuster808@...

10

sakib.sajal@...

10

trevor.gamblin@...

9

randy.macleod@...

6

Qi.Chen@...

6

yi.zhao@...

4

idadelm@...

4

mingli.yu@...

4

stacygaikovaia@...

4

hongxu.jia@...

4

raj.khem@...

4

anuj.mittal@...

3

alejandro@...

3

chee.yang.lee@...

3

mostthingsweb@...

3

pbarker@...

2

saul.wold@...

2

matthewzmd@...

2

jaewon@...

2

pokylinux@...

2

ydirson@...

2

jeanmarie.lemetayer@...

2

jon.mason@...

2

mhalstead@...

1

aehs29@...

1

Martin.Jansa@...

1

nicolas.dechesne@...

1

kergoth@...

1

kamensky@...

1

sangeeta.jain@...

1

akuster@...

1

matt.ranostay@...

1

dl9pf@...

1

joe.slater@...

1

twoerner@...

1

mark.hatle@...

1

liezhi.yang@...

1

shachar@...

1

maxime.roussinbelanger@...

1

kexin.hao@...

1

mshah@...

1

Grand Total

271

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Yocto Project Newcomer & Unassigned Bugs - Help Needed

Stephen Jolley
 

All,

 

The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project.  If anyone can help, please take ownership of the bug and send patches!  If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 344 unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out with these.  Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.  There are also roughly four different "priority" classes right now, “3.2”, “3.3, "3.99" and "Future", the more pressing/urgent issues being in "3.2" and then “3.3”.

 

Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).  The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Re: BITBAKE HANGS

Davis, Michael
 

QTWebengine needs a considerable amount of RAM to compile and link relative to the rest of Yocto.

Normally around 12-16GB.  Less than that and the system tends to hang.

 

 

 

From: yocto@... <yocto@...> On Behalf Of U RAVI KUMAR via lists.yoctoproject.org
Sent: Monday, January 11, 2021 11:25 AM
To: yocto@...
Subject: [yocto] BITBAKE HANGS

 

hi guys,

 

 I have encountered with a problem.I have built a custom linux for raspberrypi and included meta-openembedded,meta-raspberrypi,meta-qt5,meta-python2 layers and compiled on the bitbake. it is working fine.

I have added recipe "qtwebengine" , here i have encountered an issue i.e the system hangs. only while compiling qtwebengine system hangs.Can anyone suggest me the solution.So that i canovercome and proceed fiurther..

 

Thanks and regards,

ravikumar



CONFIDENTIALITY NOTICE:

This e-mail transmission and any documents, files or previous e-mail messages attached to it may contain information that is confidential, protected by the attorney/client or other privileges, and may constitute non-public information. It is intended to be conveyed only to the designated recipient(s) named above.

Any unauthorized use, reproduction, forwarding, distribution or other dissemination of this transmission is strictly prohibited and may be unlawful. If you are not an intended recipient of this email transmission, please notify the sender by return e-mail and permanently delete any record of this transmission. Your cooperation is appreciated. To find out more Click Here.


BITBAKE HANGS

U RAVI KUMAR <uppadaravi2511@...>
 

hi guys,

 I have encountered with a problem.I have built a custom linux for raspberrypi and included meta-openembedded,meta-raspberrypi,meta-qt5,meta-python2 layers and compiled on the bitbake. it is working fine.
I have added recipe "qtwebengine" , here i have encountered an issue i.e the system hangs. only while compiling qtwebengine system hangs.Can anyone suggest me the solution.So that i canovercome and proceed fiurther..

Thanks and regards,
ravikumar


Re: insmod - huawei E3372h kernel module

Zoltan Kerenyi Nagy
 

I managed to bitbake without errors/warning the 2 additional modules, however I cannot load those modules manually on the device:

http://paste.ubuntu.com/p/My4x5j3t4R/

Do you you have any idea?
--
Zolee


Re: Python3-native illegal instruction on poky dunfell

Daniela-Marinela Bistrean
 

Thank you very much for your response!

I have only one builder and the sstate is not shared. Additionally I also tried building on the zeus branch and the build fails with the same error (illegal instruction) but this time at do_configure task. And do_configure calls the same python3-native with setup.py but with a different parameter.

Any help or hint is appreciated.

On Mon, 11 Jan 2021 at 14:43, Ross Burton <ross@...> wrote:
Are you sharing sstate between multiple builders?

Ross

On Mon, 11 Jan 2021 at 08:58, Daniela-Marinela Bistrean
<daniela.marinela.bistrean@...> wrote:
>
> Hello community,
>
> I am trying to build core-image-minimal using poky only, on the dunfell branch. On certain machines the build fails unexpectedly with the following error:
> Build Configuration:
> BB_VERSION           = "1.46.0"
> BUILD_SYS            = "x86_64-linux"
> NATIVELSBSTRING      = "universal"
> TARGET_SYS           = "x86_64-poky-linux"
> MACHINE              = "qemux86-64"
> DISTRO               = "poky"
> DISTRO_VERSION       = "3.1.4"
> TUNE_FEATURES        = "m64 core2"
> TARGET_FPU           = ""
> meta
> meta-poky
> meta-yocto-bsp       = "dunfell:cd3abf42dae2310ecaa8a97b2c08378a9f6e1282"
>
> Initialising tasks: 100% |####################################################################################################################################################################| Time: 0:00:11
> Sstate summary: Wanted 1025 Found 0 Missed 1025 Current 126 (0% match, 10% complete)
> NOTE: Executing Tasks
> ERROR: python3-setuptools-native-45.2.0-r0 do_compile: 'python3 setup.py build ' execution failed.
> ERROR: python3-setuptools-native-45.2.0-r0 do_compile: Execution of '/home/builder/src/build_yocto-test/tmp/work/x86_64-linux/python3-setuptools-native/45.2.0-r0/temp/run.do_compile.141' failed with exit code 1:
> Illegal instruction (core dumped)
> WARNING: exit code 1 from a shell command.
>
> ERROR: Logfile of failure stored in: /home/builder/src/build_yocto-test/tmp/work/x86_64-linux/python3-setuptools-native/45.2.0-r0/temp/log.do_compile.141
> Log data follows:
> | DEBUG: Executing shell function do_compile
> | Illegal instruction (core dumped)
> | ERROR: 'python3 setup.py build ' execution failed.
> | WARNING: exit code 1 from a shell command.
> | ERROR: Execution of '/home/builder/src/build_yocto-test/tmp/work/x86_64-linux/python3-setuptools-native/45.2.0-r0/temp/run.do_compile.141' failed with exit code 1:
> | Illegal instruction (core dumped)
> | WARNING: exit code 1 from a shell command.
> |
> ERROR: Task (virtual:native:/home/builder/src/poky/meta/recipes-devtools/python/python3-setuptools_45.2.0.bb:do_compile) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 576 tasks of which 572 didn't need to be rerun and 1 failed.
>
> The do_compile task executes the following:
> do_compile() {
>     distutils3_do_compile
> }
>
> distutils3_do_compile() {
>         cd /home/builder/src/build_sw.sys.icp21/tmp/work/x86_64-linux/python3-setuptools-native/45.2.0-r0/setuptools-45.2.0
>         NO_FETCH_BUILD=1 \
>         STAGING_INCDIR=/home/builder/src/build_sw.sys.icp21/tmp/work/x86_64-linux/python3-setuptools-native/45.2.0-r0/recipe-sysroot-native/usr/include \
>         STAGING_LIBDIR=/home/builder/src/build_sw.sys.icp21/tmp/work/x86_64-linux/python3-setuptools-native/45.2.0-r0/recipe-sysroot-native/usr/lib \
>         /home/builder/src/build_sw.sys.icp21/tmp/work/x86_64-linux/python3-setuptools-native/45.2.0-r0/recipe-sysroot-native/usr/bin/python3-native/python3 /home/builder/src/build_sw.sys.icp21/tmp/work/x86_64-linux/python3-setuptools-native/45.2.0-r0/setuptools-45.2.0/setup.py \
>         build --build-base=/home/builder/src/build_sw.sys.icp21/tmp/work/x86_64-linux/python3-setuptools-native/45.2.0-r0/build  || \
>         bbfatal_log "'python3 setup.py build ' execution failed."
> }
>
> On this particular machine the build fails even when it is tried out from within a container. The configuration of this machine is:
> Distributor ID: Ubuntu
> Description: Ubuntu 18.04.5 LTS
> Release: 18.04
> Codename: bionic
>
> Linux vm 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
>
> 4 x Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz
>
> The python3-native binary generated by Yocto works and I can run it on the host. I have identified that setup.py file of python3-setuptools-native recipe, part of do_compile fails with illegal instruction when trying to import setuptools. On other machines the build has no issues. The machine with issues is under a VPN and a proxy (company's machine).
>
> Do you have any hint as why this might happen?
>
> Thank you and looking forward to your feedback,
> Daniela-Mărinela Bistrean
>
>
>


--
Cu deosebită consideraţie,
Daniela-Mărinela Bistrean


Re: [error-report-web][PATCH] report-error.bbclass: Add layer and bitbake version info to error report

Milan Shah
 

Hi All,

This is a Gentle Reminder to review this Patch.

-----------------------
Thanks & Regards,
Milan Shah
MontaVista Software, Bangalore, India


On Wed, Jan 6, 2021 at 7:09 PM Milan Shah <mshah@...> wrote:
Instead of just providing local.conf info, add layer names and their
revisions with bitbake version information into error report
makes it easier to understand and reproduce failed build.

[YOCTO #9700]

Signed-off-by: Milan Shah <mshah@...>
---
 meta/classes/report-error.bbclass | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/meta/classes/report-error.bbclass b/meta/classes/report-error.bbclass
index 1a12db1..9cb6b0b 100644
--- a/meta/classes/report-error.bbclass
+++ b/meta/classes/report-error.bbclass
@@ -6,6 +6,8 @@
 #
 # Licensed under the MIT license, see COPYING.MIT for details

+inherit base
+
 ERR_REPORT_DIR ?= "${LOG_DIR}/error-report"

 def errorreport_getdata(e):
@@ -64,6 +66,8 @@ python errorreport_handler () {
             data['failures'] = []
             data['component'] = " ".join(e.getPkgs())
             data['branch_commit'] = str(base_detect_branch(e.data)) + ": " + str(base_detect_revision(e.data))
+            data['bitbake_version'] = e.data.getVar("BB_VERSION")
+            data['layer_version'] = get_layers_branch_rev(e.data)
             data['local_conf'] = get_conf_data(e, 'local.conf')
             data['auto_conf'] = get_conf_data(e, 'auto.conf')
             lock = bb.utils.lockfile(datafile + '.lock')
--
2.7.4


Re: Python3-native illegal instruction on poky dunfell

Ross Burton
 

Are you sharing sstate between multiple builders?

Ross

On Mon, 11 Jan 2021 at 08:58, Daniela-Marinela Bistrean
<daniela.marinela.bistrean@gmail.com> wrote:

Hello community,

I am trying to build core-image-minimal using poky only, on the dunfell branch. On certain machines the build fails unexpectedly with the following error:
Build Configuration:
BB_VERSION = "1.46.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "3.1.4"
TUNE_FEATURES = "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp = "dunfell:cd3abf42dae2310ecaa8a97b2c08378a9f6e1282"

Initialising tasks: 100% |####################################################################################################################################################################| Time: 0:00:11
Sstate summary: Wanted 1025 Found 0 Missed 1025 Current 126 (0% match, 10% complete)
NOTE: Executing Tasks
ERROR: python3-setuptools-native-45.2.0-r0 do_compile: 'python3 setup.py build ' execution failed.
ERROR: python3-setuptools-native-45.2.0-r0 do_compile: Execution of '/home/builder/src/build_yocto-test/tmp/work/x86_64-linux/python3-setuptools-native/45.2.0-r0/temp/run.do_compile.141' failed with exit code 1:
Illegal instruction (core dumped)
WARNING: exit code 1 from a shell command.

ERROR: Logfile of failure stored in: /home/builder/src/build_yocto-test/tmp/work/x86_64-linux/python3-setuptools-native/45.2.0-r0/temp/log.do_compile.141
Log data follows:
| DEBUG: Executing shell function do_compile
| Illegal instruction (core dumped)
| ERROR: 'python3 setup.py build ' execution failed.
| WARNING: exit code 1 from a shell command.
| ERROR: Execution of '/home/builder/src/build_yocto-test/tmp/work/x86_64-linux/python3-setuptools-native/45.2.0-r0/temp/run.do_compile.141' failed with exit code 1:
| Illegal instruction (core dumped)
| WARNING: exit code 1 from a shell command.
|
ERROR: Task (virtual:native:/home/builder/src/poky/meta/recipes-devtools/python/python3-setuptools_45.2.0.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 576 tasks of which 572 didn't need to be rerun and 1 failed.

The do_compile task executes the following:
do_compile() {
distutils3_do_compile
}

distutils3_do_compile() {
cd /home/builder/src/build_sw.sys.icp21/tmp/work/x86_64-linux/python3-setuptools-native/45.2.0-r0/setuptools-45.2.0
NO_FETCH_BUILD=1 \
STAGING_INCDIR=/home/builder/src/build_sw.sys.icp21/tmp/work/x86_64-linux/python3-setuptools-native/45.2.0-r0/recipe-sysroot-native/usr/include \
STAGING_LIBDIR=/home/builder/src/build_sw.sys.icp21/tmp/work/x86_64-linux/python3-setuptools-native/45.2.0-r0/recipe-sysroot-native/usr/lib \
/home/builder/src/build_sw.sys.icp21/tmp/work/x86_64-linux/python3-setuptools-native/45.2.0-r0/recipe-sysroot-native/usr/bin/python3-native/python3 /home/builder/src/build_sw.sys.icp21/tmp/work/x86_64-linux/python3-setuptools-native/45.2.0-r0/setuptools-45.2.0/setup.py \
build --build-base=/home/builder/src/build_sw.sys.icp21/tmp/work/x86_64-linux/python3-setuptools-native/45.2.0-r0/build || \
bbfatal_log "'python3 setup.py build ' execution failed."
}

On this particular machine the build fails even when it is tried out from within a container. The configuration of this machine is:
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic

Linux vm 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

4 x Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz

The python3-native binary generated by Yocto works and I can run it on the host. I have identified that setup.py file of python3-setuptools-native recipe, part of do_compile fails with illegal instruction when trying to import setuptools. On other machines the build has no issues. The machine with issues is under a VPN and a proxy (company's machine).

Do you have any hint as why this might happen?

Thank you and looking forward to your feedback,
Daniela-Mărinela Bistrean



Re: Single page view of a particular manual

Vasyl Vavrychuk <vvavrychuk@...>
 

Hi, Nicolas,

Now, it looks like something changed.

Opening https://docs.yoctoproject.org/bitbake/, then choosing
"All-in-one 'Mega' Manual" leads to what I need: single page BitBake
User Manual - https://docs.yoctoproject.org/bitbake/singleindex.html

But there are few more issues.

1. Open https://docs.yoctoproject.org/bitbake/index.html. Select on
the top has entries "Individual Webpages" and "All-in-one 'Mega'
Manual". The problem is that entry "All-in-one 'Mega' Manual" now does
not reflects to the current behavior. Suggest to replace "All-in-one
'Mega' Manual" with "Single Webpage".

2. Open https://docs.yoctoproject.org/bitbake/. Version select at the
top with options "3.2.1", "3.1.4", etc. are not working.

Thanks,
Vasyl

On Mon, Nov 16, 2020 at 6:27 PM Nicolas Dechesne
<nicolas.dechesne@linaro.org> wrote:

hi Vasyl,

On Mon, Nov 16, 2020 at 12:55 PM Vasyl Vavrychuk <vvavrychuk@gmail.com> wrote:

Hi, Nicolas,

Thank you for your reply.

On Sun, Nov 15, 2020 at 8:06 PM Nicolas Dechesne
<nicolas.dechesne@linaro.org> wrote:

Can you please describe what you are doing in the webpage? It should
You need to select "All in one Mega manual" in the
dropdown menu on the top left corner of the page. When you do that, it
should bring you to this URL:
https://docs.yoctoproject.org/singleindex.html

Which contains the whole YP docs in a 'single' html page.
But as far as I remember, previously I could have a single page view
of a particular manual, for example "Development Tasks Manual", etc.
It is much more useful than complete single page view of all documents
at the same time (but this one is useful too in some cases).
Ah, you're right. It was possible with the previous docs, but not
anymore. With the Sphinx based docs the whole Yocto Project docs is
just "one set", not a collection of 'manuals'. So currently the single
html page includes the entire documentation set.

There is no 'easy' way to change that though. I am definitely
interested to gather more feedback about that. We made a conscious
choice to get this way, It's different, and if it's causing more pain,
we should know and discuss..

I heard complaints before that we had too 'many' manuals, and it was
hard to know which one to open, which is the opposite of what you are
asking ;)

let's see if we can gather more feedback.


nativesdk-binutils sysroot bug?

Kenth Eriksson
 

I have added native gcc support to an ARM Yocto SDK. But the native compiler does not work when passing the sysroot argument to the compiler.

kenth@se-kenth-lx yocto-xr $ x86_64-xr-linux-gcc test.c
kenth@se-kenth-lx yocto-xr $ x86_64-xr-linux-gcc test.c --sysroot=/opt/infn-xr/1.0/sysroots/x86_64-xr-linux
/opt/infn-xr/1.0/sysroots/x86_64-xr-linux/usr/lib/gcc/x86_64-xr-linux/9.2.0/../../../../x86_64-xr-linux/bin/ld: cannot find /opt/infn-xr/1.0/sysroots/x86_64-xr-linux/lib/libc.so.6 inside /opt/infn-xr/1.0/sysroots/x86_64-xr-linux
/opt/infn-xr/1.0/sysroots/x86_64-xr-linux/usr/lib/gcc/x86_64-xr-linux/9.2.0/../../../../x86_64-xr-linux/bin/ld: cannot find /opt/infn-xr/1.0/sysroots/x86_64-xr-linux/usr/lib/libc_nonshared.a inside /opt/infn-xr/1.0/sysroots/x86_64-xr-linux
/opt/infn-xr/1.0/sysroots/x86_64-xr-linux/usr/lib/gcc/x86_64-xr-linux/9.2.0/../../../../x86_64-xr-linux/bin/ld: cannot find /opt/infn-xr/1.0/sysroots/x86_64-xr-linux/lib/ld-linux-x86-64.so.2 inside /opt/infn-xr/1.0/sysroots/x86_64-xr-linux
collect2: error: ld returned 1 exit status

Error trace seems to incorrectly tell that libc is missing on that path

kenth@se-kenth-lx yocto-xr $ ls -l /opt/infn-xr/1.0/sysroots/x86_64-xr-linux/lib/libc.so.6
lrwxrwxrwx 1 root root 12 Jan 11 10:33 /opt/infn-xr/1.0/sysroots/x86_64-xr-linux/lib/libc.so.6 -> libc-2.30.so*
kenth@se-kenth-lx yocto-xr $

The sysroot argument works when only compiling the source file (no linking)
kenth@se-kenth-lx yocto-xr $ x86_64-xr-linux-gcc -c test.c -o test.o --sysroot=/opt/infn-xr/1.0/sysroots/x86_64-xr-linux

But when gcc invokes binutils with sysroot argument then it fails. Doing a strace on the invocation of gcc with sysroot shows that sometimes the sysroot path is concatenated twice;

[pid 4197] openat(AT_FDCWD, "/opt/infn-xr/1.0/sysroots/x86_64-xr-linux//opt/infn-xr/1.0/sysroots/x86_64-xr-linux/lib/libc.so.6", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 4197] write(2, "/opt/infn-xr/1.0/sysroots/x86_64"..., 110) = 110

The arm compiler has a compiled sysroot (as defined in the bb recipe)
kenth@se-kenth-lx yocto-xr $ aarch64-xr-linux-gcc --print-sysroot
/not/exist
kenth@se-kenth-lx yocto-xr $

whereas the native x86 compiler does not have a compiled sysroot

kenth@se-kenth-lx yocto-xr $ x86_64-xr-linux-gcc --print-sysroot
kenth@se-kenth-lx yocto-xr $

If I symlink the path to mitigate the concatenation effect into binutils then it all works.

Known issue? How to resolve?


Re: insmod - huawei E3372h kernel module

Zoltan Kerenyi Nagy
 

Hi, Im doing this:

KERNEL_MODULE_AUTOLOAD += "ncm_driver"KERNEL_MODULE_PROBECONF += "ncm_driver"cdc_ncm = "options ncm_driver iProduct=USB_Host_Driver_for_Network_Control_Model iManufacturer=NCM"
KERNEL_MODULE_AUTOLOAD += "wmc_device_managment"KERNEL_MODULE_PROBECONF += "wmc_device"cdc_wdm = "options wmc_device iProduct=USB_CDC_WCM_Device_Management iManufacturer=WMC"
KERNEL_MODULE_AUTOLOAD += "lte"KERNEL_MODULE_PROBECONF += "lte"huawei_cdc_ncm = "options lte iProduct=E3372h iManufacturer=Huawei"

Im very curious. I think the cdc_ncm and cdc_wdm should be inserted before huawei_cdc_ncm
 
--
Zolee

1961 - 1980 of 53914