[lsb-discuss] LSB Complianced yocto toolchain
Ravi Ranjan Chobey
Ravi.Chobey at kpit.com
Wed Oct 8 11:38:53 UTC 2014
My requirement is to check whether the toolchain built from Yocto framework is LSB complianced or not.
I don't know how to check for that. After doing some googling, i am following the below mentioned approach for that.
The procedure which i am following is mentioned below:
1. We have built one LSB complianced toolchain.I have used the below mentioned toolchain for building LSB complianced toolchain.
2. After referring the below mentioned link:
3. Export the path of qmtest binary,LD_LIBRARY_PATH and QMTEST_CLASS_PATH
4. Source the environment path for generated LSB complianced toolchain.
5. I have added IMAGE_INSTALL_append = " python python-modules" in local.conf of build.
6. Execute : ./doc/lsb-test-libstdcpp-4.1.0/build_binary_testsuite (Path of libstdcpp_4.1.0) (i586-poky-linux-g++)
7. After executing this build_binary_testsuite, we are getting the below mentioned error:
'import site' failed; use -v for traceback
Traceback (most recent call last):
File "/opt/lsb/appbat/bin/qmtest", line 67, in ?
ImportError: No module named os
A journal file has been created as: /home/ravi/lsb-dist-testkit/opt/lsb/test/libstdcpp_4.1.0/./v3db/journal.201409301726
The journal file will be having no results.
Please provide your comments on that and let me know where i am going wrong.
From: lsb-discuss-bounces at lists.linux-foundation.org [mailto:lsb-discuss-bounces at lists.linux-foundation.org] On Behalf Of Mats Wichmann
Sent: Monday, October 06, 2014 7:07 PM
To: lsb-discuss at lists.linux-foundation.org
Subject: Re: [lsb-discuss] LSB Complianced yocto toolchain
On 09/29/14 05:53, Ravi Ranjan Chobey wrote:
> Hi All,
> I have made LSB compliance Toolchain using Yocto.
> The procedure is mentioned in:
> I have extracted the "libstdcpp_4.1.0" from linux-dist-testkit and I
> am getting A "run_test" script, I am able to run "run_test" script and
> I am able to See that nearly 90% of testcases are passing and 10 % are untested test cases.
> After doing some googling, I came know that, the run_test script is using "lsbcc"
> In background to generated those results.
> Now I am following another link to use the Toolchain build using Yocto
> distribution and I am using the below mentioned command for that:
> /home/ravi/lsb-dist-testkit/opt/lsb/test/libstdcpp_4.1.0 i586-windriver-linux-g++ (I have installed qmtest-2.4 version and exported LD_LIBRARY_PATH), but getting the below mentioned errors:
> [ravi at d-8396 test]$
> /home/ravi/lsb-dist-testkit/opt/lsb/test/libstdcpp_4.1.0 i586-windriver-linux-g++ 'import site' failed; use -v for traceback Traceback (most recent call last):
> File "./../doc/lsb-test-libstdcpp-4.1.0/build_binary_testsuite", line 23, in ?
> import os
> ImportError: No module named os
> Please provide your inputs and let me know if I am missing anything.
I'm not seeing that anyone responded to you, sorry about that.
What are you trying to do? You should not be rebuilding the C++ testsuite for compliance testing, unless you feel you need to do that only for the purposes of debugging.
the "import os" message comes from python. The jig wrapping around the lsb-test-libstdcpp test suite is written in python - it is called qmtest. I've never seen a Python installation that does not have the os module available (it is a mandatory part of the language, not a option), but that seems to be the complaint here.
lsb-discuss mailing list
lsb-discuss at lists.linux-foundation.org
This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails.
More information about the lsb-discuss