From: "Peter Bergin" <peter@berginkonsult.se>
To: "meta-freescale@lists.yoctoproject.org"
<meta-freescale@lists.yoctoproject.org>
Subject: Strange build error first time on community bsp master branch
Date: Thu, 4 Mar 2021 23:15:55 +0100 [thread overview]
Message-ID: <68dbaa47-57c1-0157-d07d-9df6c5352ef3@berginkonsult.se> (raw)
Hi,
following these steps to build master branch has a really strange
behavior. First build with bitbake bails out hard with tons of WARNINGS
and ends up with an error in sstate.bbclass.
$ repo init -u
https://github.com/Freescale/fsl-community-bsp-platform -b master
$ repo sync
$ EULA=1 MACHINE=imx8mm-lpddr4-evk DISTRO=poky source
setup-environment build
$ bitbake core-image-base
Here are examples of the WARNING:
----------------
WARNING:
/storage/yocto/test2/sources/poky/meta/recipes-extended/shadow/shadow_4.8.1.bb:
Variable key PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}compilerlibs
(gcc-runtime) replaces original key
PREFERRED_PROVIDER_virtual/x86_64-pokysdk-linux-compilerlibs
(nativesdk-gcc-runtime).
WARNING:
/storage/yocto/test2/sources/meta-openembedded/meta-python/recipes-devtools/python/python3-dateutil_2.8.1.bb:
Variable key PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}compilerlibs
(gcc-runtime) replaces original key
PREFERRED_PROVIDER_virtual/x86_64-pokysdk-linux-compilerlibs
(nativesdk-gcc-runtime).
-----------------
and in the end of the parsing:
-----------------
> spec, extrapath, tname = getpathcomponents(tid, d)
File "/storage/yocto/test2/sources/poky/meta/classes/sstate.bbclass",
line 877, in
getpathcomponents(task='virtual:native:/storage/yocto/test2/sources/poky/meta/recipes-devtools/perl/libxml-parser-perl_2.46.bb:do_populate_sysroot',
d=<bb.data_smart.DataSmart object at 0x7fd579d6adf0>):
if splithashfn[0] == "True":
> extrapath = d.getVar("NATIVELSBSTRING") + "/"
else:
TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'
Summary: There were 1675 WARNING messages shown.
Summary: There were 6 ERROR messages shown, returning a non-zero exit code.
-----------------
The strange thing is that if the build is restarted again with 'bitbake
core-image-base' the build starts fine and works as expected.
I have tried to narrow this down a bit and my wild guess is that this
has something with setup-environment script to do. My build host is
Ubuntu 20.10 (that I know is not a validated build host).
Here is an experiment where I create one build dir with
setup-environment this ends up in the error described above and works
the second time. Then I create a new build dir with oe-init-build-env
and then copy local.conf and bblayers.conf from the first build dir.
$ EULA=1 MACHINE=imx6qdlsabresd DISTRO=poky source
setup-environment build
$ bitbake core-image-base
<ERROR>
$ cd ..
$ . ./sources/poky/oe-init-build-env build2
$ cp ../build/conf/bblayers.conf conf/
$ cp ../build/conf/local.conf conf/
$ bitbake core-image-base
<OK>
Someone with more insight in setup-environment script and bitbake that
have an idea?
Regards,
/Peter
next reply other threads:[~2021-03-04 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 22:15 Peter Bergin [this message]
2021-03-08 11:30 ` [meta-freescale] Strange build error first time on community bsp master branch Otavio Salvador
2021-03-08 12:16 ` Peter Bergin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=68dbaa47-57c1-0157-d07d-9df6c5352ef3@berginkonsult.se \
--to=peter@berginkonsult.se \
--cc=meta-freescale@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).