I want to verify that my sstate mirror is used properly. I added it to the SSTATE_MIRRORS variable. How can I check how much is re-used from that sstate-mirror
When inherited globally, prints statistics at the end of the build on sstate re-use. Add to your local.conf:
USER_CLASSES += "buildstats buildstats-summary"
If sstate works in general, you can see something like:
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Running setscene task 118 of 155 (virtual:native:/home/lulianhao/poky-build/edwin/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot_setscene)
NOTE: Running setscene task 119 of 155 (/home/lulianhao/poky-build/edwin/poky/meta/recipes-devtools/quilt/quilt-native_0.48.bb:do_populate_sysroot_setscene)
You also should see how much packages are re-used from the sstate mirror
Checking sstate mirror object availability: 100% |##########################################################################################################################################| Time: 0:00:47
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 5119 tasks of which 5104 didn't need to be rerun and all succeeded.
NOTE: Writing buildhistory
NOTE: Build completion summary:
NOTE: do_populate_sysroot: 0.0% sstate reuse(0 setscene, 1 scratch)
NOTE: do_package_qa: 0.0% sstate reuse(0 setscene, 1 scratch)
NOTE: do_package: 0.0% sstate reuse(0 setscene, 1 scratch)
NOTE: do_packagedata: 0.0% sstate reuse(0 setscene, 1 scratch)
NOTE: do_package_write_rpm: 0.0% sstate reuse(0 setscene, 1 scratch)
NOTE: do_populate_lic: 0.0% sstate reuse(0 setscene, 1 scratch)
https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#ref-classes-buildstats
Related
I switched from Perl 5.30 to Perl 5.36 and using Mojolicious 8.33. I tried installing Mango::BSON::ObjectID using CPAN.
cpan Mango::BSON::ObjectID
But it was throwing errors.
Test Summary Report
t/bson.t (Wstat: 256 Tests: 182 Failed: 1)
Failed test: 106
Non-zero exit status: 1
Files-13, Tests=205, 4 wallclock secs ( 0.05 usr 0.01 sys+ 1.89
cusr 0.22 csys=2.17 CPU)
Result: FAIL
Failed 1/13 test programs. 1/205 subtests failed.
make: *** [Makefile:942: test_dynamic] Error 255
ODC/Mango-1.30.tar.gz
/usr/bin/make test NOT OK
//hint// to see the cpan testers results for installing this
module, try:
reports ODC/Mango-1.38.tar.gz
So, I just want to know if Mango is supported in Perl 5.36.0 or not. And if it is not being supported, then what is the alternative to Mango?
I'm trying to build a core-image-minimal recipe on Ubuntu 20.04 in VirtualBox for Raspberry Pi3 board (~2GB RAM, 100 GB storage allowed). But facing a new issue while baking the image. In the local.conf file I've removed "tar.xz ext3" from "IMAGE_FSTYPES = ""tar.xz ext3 rpi-sdimg"" then the image baked successfully without any error, but not supporting the I2C & UART. But when I reverted the above-mentioned change it's throwing errors.
ERROR:
core-image-minimal-1.0-r0 do_image_tar: Execution of '/home/pranav/poky/build/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/run.do_image_tar.2549' failed with exit code 1
Logfile of failure stored in: /home/pranav/poky/build/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_image_tar.2549
Please, let me know what is the solution.
Complete error :
pranav#Pranav:~$ cd poky
pranav#Pranav:~/poky$ source oe-init-build-env
### Shell environment set up for builds. ###
You can now run 'bitbake <target>'
Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-ide-support
You can also run generated qemu images with a command like 'runqemu qemux86'
Other commonly useful commands are:
- 'devtool' and 'recipetool' handle common recipe tasks
- 'bitbake-layers' handles common layer tasks
- 'oe-pkgdata-util' handles common target package tasks
pranav#Pranav:~/poky/build$ bitbake core-image-minimal
Loading cache: 100% |###################################################################################################| Time: 0:00:02
Loaded 3295 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.46.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "raspberrypi3"
DISTRO = "poky"
DISTRO_VERSION = "3.1.14"
TUNE_FEATURES = "arm vfp cortexa7 neon vfpv4 thumb callconvention-hard"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "dunfell:3d5dd4dd8d66650615a01cd210ff101daa60c0df"
meta-raspberrypi = "dunfell:934064a01903b2ba9a82be93b3f0efdb4543a0e8"
meta-oe
meta-multimedia
meta-networking
meta-python = "dunfell:ec978232732edbdd875ac367b5a9c04b881f2e19"
Initialising tasks: 100% |##############################################################################################| Time: 0:00:10
Sstate summary: Wanted 2 Found 0 Missed 2 Current 1135 (0% match, 99% complete)
NOTE: Executing Tasks
ERROR: core-image-minimal-1.0-r0 do_image_tar: Execution of '/home/pranav/poky/build/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/run.do_image_tar.2549' failed with exit code 1
ERROR: Logfile of failure stored in: /home/pranav/poky/build/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_image_tar.2549
Log data follows:
| DEBUG: Executing python function set_image_size
| DEBUG: 8013.200000 = 6164 * 1.300000
| DEBUG: 8192.000000 = max(8013.200000, 8192)[8192.000000] + 0
| DEBUG: 8192.000000 = int(8192.000000)
| DEBUG: 8192 = aligned(8192)
| DEBUG: returning 8192
| DEBUG: Python function set_image_size finished
| DEBUG: Executing shell function do_image_tar
| xz: Memory usage limit is too low for the given filter setup.
| xz: 1,250 MiB of memory is required. The limit is 954 MiB.
| WARNING: exit code 1 from a shell command.
| ERROR: Execution of '/home/pranav/poky/build/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/run.do_image_tar.2549' failed with exit code 1
ERROR: Task (/home/pranav/poky/meta/recipes-core/images/core-image-minimal.bb:do_image_tar) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3053 tasks of which 3051 didn't need to be rerun and 1 failed.
Summary: 1 task failed:
/home/pranav/poky/meta/recipes-core/images/core-image-minimal.bb:do_image_tar
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
Could someone please give me advice to make an openbmc image for Raspberrypi platform ?
Before I tried, I looked through related documents and believed an openbmc image can be worked on Raspberrypi.
Like OpenBMC with Raspberry Pi (2 or 3) and build bmcweb?
and https://kevinleeblog.github.io/project1/2019/11/25/openbmc-for-raspberry-pi-zero/.
So, I followed these instructions and tried the following steps.
#1: Git clone openbmc.git to my local PC.
tm#tm-VB1:~/Rpi4-64$ git clone https://github.com/openbmc/openbmc.git
Snip the logs but it looks no problem.
Receiving objects: 100% (182121/182121), 84.10 MiB | 5.55 MiB/s, done.
Resolving deltas: 100% (96860/96860), done.
#2: set TEMPLATECONF for raspberrypi
tm#tm-VB1:~/Rpi4-64$ export TEMPLATECONF=meta-evb/meta-evb-raspberrypi/conf
tm#tm-VB1:~/Rpi4-64$ echo $TEMPLATECONF
meta-evb/meta-evb-raspberrypi/conf
#3: set up the environment by "openbmc-env"
tm#tm-VB1:~/Rpi4-64/openbmc$ . openbmc-env
### Initializing OE build env ###
Snip the logs but it looks no problem. As you know, the script automatically creates a subdirectory,build, under openbmc.
Common targets are:
obmc-phosphor-image
tm#tm-VB1:~/Rpi4-64/openbmc/build$
#4: Change the directory and edit local.conf for my Raspberrypi platform.
tm#tm-VB1:~/Rpi4-64/openbmc/build$ cat ./conf/local.conf
Snip the log for unchanged part.
MACHINE ??= "raspberrypi4-64" <<< Change here for my platform.
DL_DIR ?= "/home/tm/Yocto/downloads" <<< Add here for build-time reduction at retry.
SSTATE_DIR ?= "/home/tm/Yocto/sstate-cache" <<< Add here for build-time reduction at retry.
#5: Change FLASH_SIZE variable based on the following sugestion. https://github.com/openbmc/openbmc/issues/3590
tm#tm-VB1:~/Rpi4-64/openbmc/meta-phosphor/classes$ cat image_types_phosphor.bbclass
Snip the log.
# Flash characteristics in KB unless otherwise noted
FLASH_SIZE ?= "131072" <<< I changed only this variable from 32768 to 131072.
#6: bitbake starts.
tm#tm-VB1:~/Rpi4-64/openbmc/bitbake obmc-phosphor-image
Then, ERROR happened.
ERROR: Logfile of failure stored in: /home/tm/Rpi/openbmc/build/tmp/work/raspberrypi-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/temp/log.do_generate_static.2055074
DEBUG: Executing python function do_generate_static
DEBUG: Executing shell function do_mk_static_nor_image
32768+0 records in
32768+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0.09147 s, 367 MB/s
DEBUG: Shell function do_mk_static_nor_image finished
DEBUG: Considering file size=495980 name=/home/tm/Rpi/openbmc/build/tmp/deploy/images/raspberrypi/u-boot.bin
DEBUG: Spanning start=0K end=512K
DEBUG: Compare needed=495980 available=524288 margin=28308
484+1 records in
484+1 records out
495980 bytes (496 kB, 484 KiB) copied, 0.00120141 s, 413 MB/s
DEBUG: Considering file size=8266960 name=/home/tm/Rpi/openbmc/build/tmp/deploy/images/raspberrypi/fitImage-obmc-phosphor-initramfs-raspberrypi-raspberrypi
DEBUG: Spanning start=512K end=4864K
>>>DEBUG: Compare needed=8266960 available=4456448 margin=-3810512
ERROR: Image '/home/tm/Rpi/openbmc/build/tmp/deploy/images/raspberrypi/fitImage-obmc-phosphor-initramfs-raspberrypi-raspberrypi' is too large!
DEBUG: Python function do_generate_static finished
It said margin=-3810512.
Now, my 2nd try.
I removed the whole openbmc directory and did the same steps above.
But this time, I change FLASH_SIZE from 32768 to 262144.
It is the same result like below.
ERROR: obmc-phosphor-image-1.0-r0 do_generate_static: Image '/home/tm/Rpi4/openbmc/build/tmp/deploy/images/raspberrypi4/u-boot.bin' is too large!
ERROR: Logfile of failure stored in: /home/tm/Rpi4/openbmc/build/tmp/work/raspberrypi4-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/temp/log.do_generate_static.2061792
ERROR: Task (/openbmc/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:do_generate_static) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3915 tasks of which 2633 didn't need to be rerun and 1 failed.
Summary: 1 task failed:
/openbmc/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:do_generate_static
Summary: There were 2 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
tm#tm-VB1:~/Rpi4/openbmc/build$ cat /home/tm/Rpi4/openbmc/build/tmp/work/raspberrypi4-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/temp/log.do_generate_static.2061792
DEBUG: Executing python function do_generate_static
DEBUG: Executing shell function do_mk_static_nor_image
32768+0 records in
32768+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0.177223 s, 189 MB/s
DEBUG: Shell function do_mk_static_nor_image finished
DEBUG: Considering file size=548224 name=/home/tm/Rpi4/openbmc/build/tmp/deploy/images/raspberrypi4/u-boot.bin
DEBUG: Spanning start=0K end=512K
>>>DEBUG: Compare needed=548224 available=524288 margin=-23936
ERROR: Image '/home/tm/Rpi4/openbmc/build/tmp/deploy/images/raspberrypi4/u-boot.bin' is too large!
DEBUG: Python function do_generate_static finished
tm#tm-VB1:~/Rpi4/openbmc/build$
It said margin=-23936.
OK. Image is too large. So,my 3rd try.
I removed the whole openbmc directory and did the same steps above.
But this time, I change FLASH_SIZE from 32768 to 9437184.
It is the same result like below.
ERROR: obmc-phosphor-image-1.0-r0 do_generate_static: Image '/home/tm/Rpi4/openbmc/build/tmp/deploy/images/raspberrypi4/u-boot.bin' is too large!
ERROR: Logfile of failure stored in: /home/tm/Rpi4/openbmc/build/tmp/work/raspberrypi4-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/temp/log.do_generate_static.2058361
ERROR: Task (/openbmc/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:do_generate_static) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3935 tasks of which 0 didn't need to be rerun and 1 failed.
Summary: 1 task failed:
/openbmc/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:do_generate_static
Summary: There were 4 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
tm#tm-VB1:~/Rpi4/openbmc$
tm#tm-VB1:~/Rpi4/openbmc$ cat /home/tm/Rpi4/openbmc/build/tmp/work/raspberrypi4-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/temp/log.do_generate_static.2058361
DEBUG: Executing python function do_generate_static
DEBUG: Executing shell function do_mk_static_nor_image
32768+0 records in
32768+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0.173685 s, 193 MB/s
DEBUG: Shell function do_mk_static_nor_image finished
DEBUG: Considering file size=548224 name=/home/tm/Rpi4/openbmc/build/tmp/deploy/images/raspberrypi4/u-boot.bin
DEBUG: Spanning start=0K end=512K
>>>DEBUG: Compare needed=548224 available=524288 margin=-23936
ERROR: Image '/home/tm/Rpi4/openbmc/build/tmp/deploy/images/raspberrypi4/u-boot.bin' is too large!
DEBUG: Python function do_generate_static finished
tm#tm-VB1:~/Rpi4/openbmc$
It said the same margin as 256MB case.
My 4th try.
I removed the whole openbmc directory and did the same steps above.
I changed MACHINE ??= "raspberrypi4-64" to "raspberrypi2"
But this time, I change FLASH_SIZE from 32768 to 33554432.
It is the same result before.
My 5th try.
I removed the whole openbmc directory and did the same steps above.
I used MACHINE ??= "raspberrypi2"
But this time, I change FLASH_SIZE from 32768 to 67108864.
It is the same result before.
After I tried several variations, it always said "image is too large" although I changed FLASH_SIZE to much much larger one.
So, I am wondering if I have missed some important configuration or it needs another parameter to fix this except FLASH_SIZE.
By the way, I tried romulus and made it.
My environment is ubuntu-20.04.2.0-desktop-amd64.
I really appreciate someone could kindly give me advice to make this work.
Interesting, I don't have a quick fix for you but I did notice the partition that is over sized is the uboot partition. The uboot is a smaller separate binary installed on the machine. It looks as if your uboot build is over 512k and the partition is set for 512k. Your flash size is massize
FLASH_SIZE = 9437184" that is more then a gig, (because FLASH_SIZE is in K)
If I were you I would first try to build an older version of openbmc for raspberry pi. (It used to work so you just need to find the commit before uboot grew to big). Use git to move back a month until you find it works.
If that does not work I would try to modify the partition table.
here is where you failing
this looks fine building the uboot image looks fine
increasing the kernel offset make if build, but the other targets in openbmc will not be happy with this solution. So maybe meta-raspberry-pi will have to override the partition table (if uboot can not be shrunk)
What ever you do, open an issue on the github and share you changes. Also use the discord, and gerrit.
I just replicated this issue. We should fix it
I am an agl and pokey newbie, and have followed the steps in https://wiki.automotivelinux.org/agl-distro/source-code
(I am running the following in a docker container)
$source meta-agl/scripts/aglsetup.sh -m qemux86-64 agl-demo agl-netboot
------------ aglsetup.sh: Starting
Configuration files already exist:
- /home/work/agl/build/conf/local.conf
- /home/work/agl/build/conf/bblayers.conf
Skipping configuration files generation.
Use option -f|--force to overwrite existing configuration.
Generating setup manifest: /home/work/agl/build/aglsetup.manifest ... OK
Generating setup file: /home/work/agl/build/agl-init-build-env ... OK
------------ aglsetup.sh: Done
Common targets are:
- meta-agl: (core system)
- agl-profile-core:
agl-image-boot
agl-image-minimal
agl-image-minimal-qa
- agl-profile-graphical:
agl-image-weston
- agl-profile-graphical-qt5:
agl-image-graphical-qt5
agl-image-graphical-qt5-crosssdk
- agl-profile-graphical-html5
agl-demo-platform-html5
- meta-agl-demo: (demo with UI)
agl-image-ivi (base for ivi targets)
agl-image-ivi-qa
agl-image-ivi-crosssdk
agl-demo-platform (* default demo target)
agl-demo-platform-qa
agl-demo-platform-crosssdk
$bitbake agl-demo-platform
This hangs in
Initialising tasks: 100% |############################################################################################| Time: 0:00:05
Sstate summary: Wanted 2729 Found 0 Missed 2729 Current 0 (0% match, 0% complete)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
No currently running tasks (16 of 7400) 0% ||
In order to debug it, I ran
$bitbake -DDD agl-demo-platform
...
DEBUG: Full skip list {'/home/work/agl/meta-agl/meta-netboot/recipes-core/images/initramfs-netboot-image.bb:do_packagedata', '/home/work/agl/meta-agl/meta-netboot/recipes-core/images/initramfs-netboot-image.bb:do_install', '/home/work/agl/meta-agl-demo/recipes-platform/images/agl-demo-platform.bb:do$
package', '/home/work/agl/meta-agl-demo/recipes-platform/images/agl-demo-platform.bb:do_compile', '/home/work/agl/meta-agl-demo/recipes-platform/imag
es/agl-demo-platform.bb:do_install', '/home/work/agl/meta-agl-demo/recipes-platform/images/agl-demo-platform.bb:do_packagedata', '/home/work/agl/meta
-agl-demo/recipes-platform/images/agl-demo-platform.bb:do_configure', '/home/work/agl/meta-agl/meta-netboot/recipes-core/images/initramfs-netboot-image.bb:do_configure', '/home/work/agl/meta-agl/meta-netboot/recipes-core/images/initramfs-netboot-image.bb:do_compile', '/home/work/agl/meta-agl/meta-netboot/recipes-core/images/initramfs-netboot-image.bb:do_package'}
DEBUG: Using runqueue scheduler 'speed'
DEBUG: Stampfile /home/work/agl/build/tmp/stamps/x86_64-linux/quilt-native/0.65-r0.do_fetch.e8a4c952a66942653e36f289eaf68ca5 not available
NOTE: Running task 1 of 7400 (/home/work/agl/external/poky/meta/recipes-devtools/quilt/quilt-native_0.65.bb:do_fetch)
DEBUG: Stampfile /home/work/agl/build/tmp/stamps/x86_64-linux/texinfo-dummy-native/1.0-r0.do_fetch.6af0fac94be624020d4ded1391838faa not available
NOTE: Running task 2 of 7400 (/home/work/agl/external/poky/meta/recipes-extended/texinfo-dummy-native/texinfo-dummy-native.bb:do_fetch)
DEBUG: Stampfile /home/work/agl/build/tmp/stamps/x86_64-linux/gnu-config-native/20180713+gitAUTOINC+30d53fc428-r0.do_fetch.66a4b9fc46062c0ab4c3d6bf6838$8ef not available
NOTE: Running task 3 of 7400 (virtual:native:/home/work/agl/external/poky/meta/recipes-devtools/gnu-config/gnu-config_git.bb:do_fetch)
DEBUG: Stampfile /home/work/agl/build/tmp/stamps/x86_64-linux/m4-native/1.4.18-r0.do_fetch.6762cc3ab39f2cedf73b612115bd959d not available
NOTE: Running task 4 of 7400 (/home/work/agl/external/poky/meta/recipes-devtools/m4/m4-native_1.4.18.bb:do_fetch)
DEBUG: Stampfile /home/work/agl/build/tmp/stamps/x86_64-linux/autoconf-native/2.69-r11.do_fetch.25fa26d4261bb5d4666677301aa59479 not available
NOTE: Running task 5 of 7400 (virtual:native:/home/work/agl/external/poky/meta/recipes-devtools/autoconf/autoconf_2.69.bb:do_fetch)
DEBUG: Stampfile /home/work/agl/build/tmp/stamps/x86_64-linux/automake-native/1.16.1-r0.do_fetch.0fd4964b1b460fad47bd3cfb55e06e3f not available
NOTE: Running task 6 of 7400 (virtual:native:/home/work/agl/external/poky/meta/recipes-devtools/automake/automake_1.16.1.bb:do_fetch)
DEBUG: Stampfile /home/work/agl/build/tmp/stamps/x86_64-linux/libtool-native/2.4.6-r0.do_fetch.fb99da9a9824dd7b876403694f7b783a not available
NOTE: Running task 7 of 7400 (/home/work/agl/external/poky/meta/recipes-devtools/libtool/libtool-native_2.4.6.bb:do_fetch)
DEBUG: Stampfile /home/work/agl/build/tmp/stamps/x86_64-linux/gettext-minimal-native/0.19.8.1-r0.do_fetch.d984cddf39092f50c5874c27f42c9627 not available
NOTE: Running task 8 of 7400 (/home/work/agl/external/poky/meta/recipes-core/gettext/gettext-minimal-native_0.19.8.1.bb:do_fetch)
DEBUG: Stampfile /home/work/agl/build/tmp/stamps/x86_64-linux/xz-native/5.2.4-r0.do_fetch.eb624201d02d0135b086909af9a87977 not available
NOTE: Running task 9 of 7400 (virtual:native:/home/work/agl/external/poky/meta/recipes-extended/xz/xz_5.2.4.bb:do_fetch)
DEBUG: Stampfile /home/work/agl/build/tmp/stamps/x86_64-linux/gmp-native/6.1.2-r0.do_fetch.d4d7e5eb8e67d572386a46cc21e57f8e not available
NOTE: Running task 10 of 7400 (virtual:native:/home/work/agl/external/poky/meta/recipes-support/gmp/gmp_6.1.2.bb:do_fetch)
DEBUG: Stampfile /home/work/agl/build/tmp/stamps/x86_64-linux/flex-native/2.6.0-r0.do_fetch.588daad6e54df2fe977b08ef749ef523 not available
NOTE: Running task 11 of 7400 (virtual:native:/home/work/agl/external/poky/meta/recipes-devtools/flex/flex_2.6.0.bb:do_fetch)
DEBUG: Stampfile /home/work/agl/build/tmp/stamps/x86_64-linux/zlib-native/1.2.11-r0.do_fetch.1fa21ab74fd7fedd15f87baac65b9dab not available
NOTE: Running task 12 of 7400 (virtual:native:/home/work/agl/external/poky/meta/recipes-core/zlib/zlib_1.2.11.bb:do_fetch)
DEBUG: Stampfile /home/work/agl/build/tmp/stamps/x86_64-linux/autoconf-archive-native/2018.03.13-r0.do_fetch.e880edd4650611bf6f65e254102ba230 not available
DEBUG: Stampfile /home/work/agl/build/tmp/stamps/x86_64-linux/autoconf-archive-native/2018.03.13-r0.do_fetch.e880edd4650611bf6f65e254102ba230 not available
NOTE: Running task 13 of 7400 (virtual:native:/home/work/agl/external/poky/meta/recipes-devtools/autoconf-archive/autoconf-archive_2018.03.13.bb:do_fetch)
DEBUG: Stampfile /home/work/agl/build/tmp/stamps/x86_64-linux/mpfr-native/4.0.1-r0.do_fetch.34c76de4a18ded6152d2ff68820420c9 not available
NOTE: Running task 14 of 7400 (virtual:native:/home/work/agl/external/poky/meta/recipes-support/mpfr/mpfr_4.0.1.bb:do_fetch)
DEBUG: Stampfile /home/work/agl/build/tmp/stamps/x86_64-linux/bison-native/3.0.4-r0.do_fetch.53556f21491498d19bb9e3b24cf725b2 not available
NOTE: Running task 15 of 7400 (virtual:native:/home/work/agl/external/poky/meta/recipes-devtools/bison/bison_3.0.4.bb:do_fetch)
DEBUG: Stampfile /home/work/agl/build/tmp/stamps/x86_64-linux/binutils-cross-x86_64/2.31.1-r0.do_fetch.14df04f9e0c741b374c8987222b85026 not available
NOTE: Running task 16 of 7400 (/home/work/agl/external/poky/meta/recipes-devtools/binutils/binutils-cross_2.31.bb:do_fetch)
When the above happens, there are the following process in ps -ef output
admin 3977 1430 0 10:48 pts/3 00:00:02 python3 /home/work/agl/external/poky/bitbake/bin/bitbake agl-demo-platform
admin 3996 1 7 10:48 ? 00:00:28 python3 /home/work/agl/external/poky/bitbake/bin/bitbake agl-demo-platform
admin 4108 3996 0 10:48 ? 00:00:00 python3 /home/work/agl/external/poky/bitbake/bin/bitbake-worker decafbad
It looks like there are 16(?) do_fetch tasks going on. I have tried waiting for an hour but bitbake does not move forward.
My container does not have strace enabled. Could someone please help me with debugging?
All the git repositories under agl directory except the following three are on branch icefish, not sure if it matters but just documenting it
external/meta-iot-cloud
* (no branch)
external/meta-python2
* (no branch)
bsp/meta-arm
* (no branch)
There are no run.do_fetch logs in $T
admin#623c5e680b76:/home/work/agl/build$ bitbake -e|grep ^T=
T="/home/work/agl/build/tmp/work/corei7-64-agl-linux/defaultpkgname/1.0-r0/temp"
/home/work/agl$ ls -l build/tmp/work/corei7-64-agl-linux/defaultpkgname/1.0-r0/temp/*
lrwxrwxrwx 1 admin admin 30 Jun 28 19:42 build/tmp/work/corei7-64-agl-linux/defaultpkgname/1.0-r0/temp/run.oecore_update_bblayers -> run.oecore_update_bblayers.369
-rw-r--r-- 1 admin admin 4565 Jun 28 19:42 build/tmp/work/corei7-64-agl-linux/defaultpkgname/1.0-r0/temp/run.oecore_update_bblayers.369
-rw-rw-r-- 1 admin admin 4565 Jun 28 18:02 build/tmp/work/corei7-64-agl-linux/defaultpkgname/1.0-r0/temp/run.oecore_update_bblayers.560
-rw-r--r-- 1 admin admin 4565 Jun 28 17:50 build/tmp/work/corei7-64-agl-linux/defaultpkgname/1.0-r0/temp/run.oecore_update_bblayers.715
-rw-r--r-- 1 admin admin 4565 Jun 28 17:16 build/tmp/work/corei7-64-agl-linux/defaultpkgname/1.0-r0/temp/run.oecore_update_bblayers.769
EDIT
There is no quilt directory in the work directory
$ pwd
/home/work/agl/build/tmp/work
$ find .
.
./corei7-64-agl-linux
./corei7-64-agl-linux/defaultpkgname
./corei7-64-agl-linux/defaultpkgname/1.0-r0
./corei7-64-agl-linux/defaultpkgname/1.0-r0/temp
./corei7-64-agl-linux/defaultpkgname/1.0-r0/temp/run.oecore_update_bblayers.560
./corei7-64-agl-linux/defaultpkgname/1.0-r0/temp/run.oecore_update_bblayers.633
./corei7-64-agl-linux/defaultpkgname/1.0-r0/temp/run.oecore_update_bblayers.369
./corei7-64-agl-linux/defaultpkgname/1.0-r0/temp/run.oecore_update_bblayers.715
./corei7-64-agl-linux/defaultpkgname/1.0-r0/temp/run.oecore_update_bblayers.769
./corei7-64-agl-linux/defaultpkgname/1.0-r0/temp/run.oecore_update_bblayers
EDIT
I could make the build start with basing my container off crops/poky-container.My container did not have the following
new user usersetup and sudoers.usersetup
execution of /usr/bin/distro-entry.sh which in turn runs /opt/poky/3.1/environment-setup-x86_64-pokysdk-linux
I am getting generation does not exist error while compiling magento. My terminal log is below
[centos#ip-172-31-5-26 ~]$ cd /var/www/html/mage
[centos#ip-172-31-5-26 mage]$ sudo php bin/magento setup:di:compile
Compilation was started.
Proxies code generation... 0/7 [>---------------------------] 0% 1 sec 42.0 MiProxies code generation... 1/7 [====>-----------------------] 14% 1 sec 46.0 MiRepositories code generation... 1/7 [====>-----------------------] 14% 1 sec 46.0 MiB
[RuntimeException]
Source class "\ProductRepositoryInterface" for "ProductRepositoryInterfaceF
actory" generation does not exist.
setup:di:compile
Please help me to resolve this issue.
Pls, try to clean folder var/generation and then try again. maybe some files was broken and need to be sure that all is up to date