Created attachment 3989 [details] Full log file $ bitbake core-image-minimal $ bitbake core-image-minimal -c populate_sdk_ext Build Configuration: BB_VERSION = "1.35.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "2.3+snapshot-20170906" TUNE_FEATURES = "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "HEAD:8b4f16a9cbbaf521461f699b7264fac2ac872581" Fails with the following error: ... <snip> ... Installed: meta-environment-extsdk-qemux86-64.x86_64_nativesdk 1.0-r8 Complete! NOTE: Added oe-repo repo from /data/master/poky/build-sato-64/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/oe-rootfs-repo 5 files removed NOTE: Executing copy_buildsystem ... DEBUG: Executing python function copy_buildsystem NOTE: Generating sstate task list... NOTE: Generating sstate-cache... NOTE: Generating sstate-cache... DEBUG: Python function copy_buildsystem finished NOTE: Executing install_tools ... DEBUG: Executing shell function install_tools Traceback (most recent call last): File "/data/master/poky/scripts/lnr", line 21, in <module> os.symlink(target, linkname) FileExistsError: [Errno 17] File exists: '../../../../layers/poky/scripts/runqemu' -> '/data/master/poky/build-sato-64/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/sdk-ext/image//opt/poky/2.3+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/runqemu' WARNING: exit code 1 from a shell command. DEBUG: Python function do_populate_sdk_ext finished ERROR: Function failed: install_tools (log file is located at /data/master/poky/build-sato-64/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/temp/log.do_populate_sdk_ext.74910)
What configuration are you using to trigger this? AFAIK it does not happen in a default build.
(In reply to comment #1) > What configuration are you using to trigger this? AFAIK it does not happen > in a default build. Nothing unusual, local.conf: SANITY_TESTED_DISTROS="" MACHINE = "qemux86-64" It seems to be 100% reproducible on my machine, I think. Tried several times, including clean builds. It could be a race (88 threads). Did not have the problem with my home slow machine. (I will confirm). Anyway, I think it is time to retire "scripts/lnr".
(In reply to comment #2) > (In reply to comment #1) > > What configuration are you using to trigger this? AFAIK it does not happen > > in a default build. > > Nothing unusual, local.conf: > SANITY_TESTED_DISTROS="" > MACHINE = "qemux86-64" > > It seems to be 100% reproducible on my machine, I think. > Tried several times, including clean builds. It could be a race (88 threads). > Did not have the problem with my home slow machine. (I will confirm). > Anyway, I think it is time to retire "scripts/lnr". Hi all, I tried to build using the same steps and configurations, but failed to reproduce it. My machine is a 22 cores (44 threads) Ubuntu workstation.
(In reply to comment #3) > (In reply to comment #2) > > (In reply to comment #1) > > > What configuration are you using to trigger this? AFAIK it does not happen > > > in a default build. > > > > Nothing unusual, local.conf: > > SANITY_TESTED_DISTROS="" > > MACHINE = "qemux86-64" > > > > It seems to be 100% reproducible on my machine, I think. > > Tried several times, including clean builds. It could be a race (88 threads). > > Did not have the problem with my home slow machine. (I will confirm). > > Anyway, I think it is time to retire "scripts/lnr". > > Hi all, I tried to build using the same steps and configurations, but failed > to reproduce it. My machine is a 22 cores (44 threads) Ubuntu workstation. I also failed to reproduce it on my home machine. The machine that does fail is fairly new, just installed OS & some software. So possibly there is a prerequisite missing. I'll dig deeper.
Not easy to reproduce. I would like to close this one, but I still have the failing environment around and I would like to come to the bottom of this.
Cannot reproduce anymore.