Bug 8615 - strange errors on SDK
Summary: strange errors on SDK
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.1
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 2.1 M1
Assignee: jia,fang
QA Contact: Yi Zhao
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-10-30 01:39 UTC by Robert Yang
Modified: 2016-01-27 06:08 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Yang 2015-10-30 01:39:22 UTC
On Ubuntu, after source SDK's environment-setup file:

$ foo (command doesn't exist)
Traceback (most recent call last):
  File "/buildarea/lyang1/sdk/sysroots/x86_64-pokysdk-linux/usr/lib/python2.7/site.py", line 553, in <module>
    main()
  File "/buildarea/lyang1/sdk/sysroots/x86_64-pokysdk-linux/usr/lib/python2.7/site.py", line 535, in main
    known_paths = addusersitepackages(known_paths)
  File "/buildarea/lyang1/sdk/sysroots/x86_64-pokysdk-linux/usr/lib/python2.7/site.py", line 266, in addusersitepackages
    user_site = getusersitepackages()
  File "/buildarea/lyang1/sdk/sysroots/x86_64-pokysdk-linux/usr/lib/python2.7/site.py", line 241, in getusersitepackages
    user_base = getuserbase() # this will also set USER_BASE
  File "/buildarea/lyang1/sdk/sysroots/x86_64-pokysdk-linux/usr/lib/python2.7/site.py", line 230, in getuserbase
    from sysconfig import get_config_var
  File "/buildarea/lyang1/sdk/sysroots/x86_64-pokysdk-linux/usr/lib/python2.7/sysconfig.py", line 10, in <module>
    'stdlib': '{base}/'+sys.lib+'/python{py_version_short}',
AttributeError: 'module' object has no attribute 'lib'

These strange erors would confuse the use which is caused by command not found helper. We can disable it.
Comment 2 Yi Zhao 2016-01-27 06:08:52 UTC
Verified with Yocto 2.0.1 (jethro/dd0ba9ea4a11ab15348d4fe3574e4b28784db82f)

There is no traceback:
$ foo
-bash: foo: command not found