Comments (25)
I can reproduce this. It seems that we are not able to run qemu-user during build which is supposed to pregenerate these files. Recent image QA checks have started to catch this. I think image should still be building even after these diags. Isn't that the case ?
from meta-riscv.
Can you try to revert dcb61db
and see if that helps ? Also getting @alistair23 here
from meta-riscv.
Dear @kraj, @jleidel.
I builded dcb61db yesterday and meet same issue.
And I encountered the problem before dcb61db.
from meta-riscv.
@pino-kim so you can confirm it was a problem before us changing
to using upstream qemu ?
from meta-riscv.
I love this repository because I send first PR here.
So every pr is comming up. I do git clone and sync, build it again.
My latest build date is Aug 28th after we comment pr 5525260 is merged.
But make it clear. check my build pc's latest commit, when I back to home right away.
To summarize the issues I encountered
3d52a33 : kernel 4.18-r7 fetch well but kernel build issue. so I commented it linux-riscv github.
e64b2ee : kernel4.18 build well but meet same issue above.
5525260 and
dcb61db : after we talk about QEMU 3.0 and I build it. meet same issue above.
I attach 5525260 do_rootfs error log #29
thank you.
from meta-riscv.
I can't confirm the bug in dcb61db; I dropped my original source to pull a refresh copy and rebase on dcb61db. The build instructions from the README.md now fail. This is tracked in Issue #28
from meta-riscv.
confirming on today's master branch that the bugs still exist. the image is not created. attempting to run qemu gives the following errors:
runqemu - INFO - Running bitbake -e...
ls: cannot access '/hdd/home/jleidel/dev/working/yocto/riscv-yocto/build/tmp-glibc/deploy/images/qemuriscv64/.qemuboot.conf': No such file or directory
runqemu - ERROR - Command 'ls -t /hdd/home/jleidel/dev/working/yocto/riscv-yocto/build/tmp-glibc/deploy/images/qemuriscv64/.qemuboot.conf' returned non-zero exit status 2
runqemu - INFO - Cleaning up
from meta-riscv.
proposed patches to OE-Core
http://lists.openembedded.org/pipermail/openembedded-core/2018-August/154993.html
fixes the problem, You can cherry-pick them or wait until they land in master.
from meta-riscv.
I am not sure if the error below this is related to this issue. But I have tried applying the patch to my build with no effect.
ERROR: core-image-full-cmdline-1.0-r0 do_rootfs: The postinstall intercept hook 'update_pixbuf_cache' failed,
can someone please help me?
from meta-riscv.
Can you retry with todays master ?
from meta-riscv.
The build still fails:
WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: busybox.postinst returned 1, marking as unpacked only, configuration required on target.
ERROR: core-image-full-cmdline-1.0-r0 do_rootfs: Postinstall scriptlets of ['busybox'] have failed. If the intention is to defer them to first boot, then please place them into pkg_postinst_ontarget_${PN} (). Deferring to first boot via 'exit 1' is no longer supported. Details of the failure are in /hdd/home/jleidel/dev/working/yocto/riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-image-full-cmdline/1.0-r0/temp/log.do_rootfs.
ERROR: core-image-full-cmdline-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /hdd/home/jleidel/dev/working/yocto/riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-image-full-cmdline/1.0-r0/temp/log.do_rootfs.6705
ERROR: Task (/hdd/home/jleidel/dev/working/yocto/riscv-yocto/openembedded-core/meta/recipes-extended/images/core-image-full-cmdline.bb:do_rootfs) failed with exit code '1'
from meta-riscv.
Please cherry-pick this commit to openembedded-core
https://patchwork.openembedded.org/patch/154406/
from meta-riscv.
Latest master has this fix now http://git.openembedded.org/openembedded-core/commit/?id=ef11c54ba99af261a70ec31091216cdd1556da24
with this you should be able to build the images again. Please update and retry
from meta-riscv.
The build still fails:
ERROR: core-image-full-cmdline-1.0-r0 do_rootfs: The postinstall intercept hook 'update_pixbuf_cache' failed, details in /hdd/home/jleidel/dev/working/yocto/riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-image-full-cmdline/1.0-r0/temp/log.do_rootfs
ERROR: core-image-full-cmdline-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /hdd/home/jleidel/dev/working/yocto/riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-image-full-cmdline/1.0-r0/temp/log.do_rootfs.14184
ERROR: Task (/hdd/home/jleidel/dev/working/yocto/riscv-yocto/openembedded-core/meta/recipes-extended/images/core-image-full-cmdline.bb:do_rootfs) failed with exit code '1'
from meta-riscv.
thanks, it seems we need more fixes. Reason is that qemu-user is failing probably a risc-v qemu issue.
we need to dig
from meta-riscv.
rootfs_log_20180906.txt
I build and get fail log too.
ERROR: core-image-full-cmdline-1.0-r0 do_rootfs: The postinstall intercept hook 'update_font_cache' failed, details in /home/pino/workspace/riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-image-full-cmdline/1.0-r0/temp/log.do_rootfs
ERROR: core-image-full-cmdline-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /home/pino/workspace/riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-image-full-cmdline/1.0-r0/temp/log.do_rootfs.14230
ERROR: Task (/home/pino/workspace/riscv-yocto/openembedded-core/meta/recipes-extended/images/core-image-full-cmdline.bb:do_rootfs) failed with exit code '1'
from meta-riscv.
log.do_rootfs.28664
Fail Log I am seeing:
NOTE: Running intercept scripts:
NOTE: > Executing update_pixbuf_cache intercept ...
NOTE: Exit code 2. Output:
/home/riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-image-full-cmdline/1.0-r0/intercept_scripts-2c03b46bc7941049a88b6c1719c35aade81b0ce5490421e7cca768bf8beb0d01/update_pixbuf_cache: 8: /home/riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-image-full-cmdline/1.0-r0/intercept_scripts-2c03b46bc7941049a88b6c1719c35aade81b0ce5490421e7cca768bf8beb0d01/update_pixbuf_cache: cannot create /home//riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-image-full-cmdline/1.0-r0/rootfs/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/../loaders.cache: Directory nonexistent
ERROR: The postinstall intercept hook 'update_pixbuf_cache' failed, details in /home/riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-image-full-cmdline/1.0-r0/temp/log.do_rootfs
DEBUG: Python function do_rootfs finished
ERROR: Function failed: do_rootfs
from meta-riscv.
Can you try adding
PACKAGE_CLASSES = "package_rpm"
in local.conf
and see if that helps ?
from meta-riscv.
dear @kraj
I will try
and report it soon.
from meta-riscv.
do_rootfs_20180921.txt
try change in local.conf
PACKAGE_CLASSES = "package_rpm
ERROR: corerror: core-image-full-cmdline-1.0-r0 do_rootfs: The postinstall intercept hook 'update_font_cache' failed, details in /home/pino/workspace/riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-image-full-cmdline/1.0-r0/temp/log.do_rootfs
ERROR: core-image-full-cmdline-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /home/pino/workspace/riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-image-full-cmdline/1.0-r0/temp/log.do_rootfs.16797
ERROR: Task (/home/pino/workspace/riscv-yocto/openembedded-core/meta/recipes-extended/images/core-image-full-cmdline.bb:do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2913 tasks of which 5 didn't need to be rerun and 1 failed.
Summary: 1 task failed:
/home/pino/workspace/riscv-yocto/openembedded-core/meta/recipes-extended/images/core-image-full-cmdline.bb:do_rootfs
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
from meta-riscv.
hmm I just build latest master and dont see this error. Can you post the Build Configuration which is printed by bitbake at the beginning of build
from meta-riscv.
@kraj
hmm really? fine news
I build it yesterday. So I will rebuild it report soon.
you want to see. Host bitbake information when build is start?
from meta-riscv.
@kraj
I set my pc like Readme file.
and change PACKAGE_CLASSES = "package_rpm"
in riscv-yocto/build/conf/local.conf
.
Can you find what's wrong in my build environment?
Build Configuration:
BB_VERSION = "1.39.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "ubuntu-16.04"
TARGET_SYS = "riscv64-oe-linux"
MACHINE = "qemuriscv64"
DISTRO = "nodistro"
DISTRO_VERSION = "nodistro.0"
TUNE_FEATURES = "riscv64 littleendian"
meta = "work:957a2f95b839f2d871c658d6e8ea8c0f4d6c41e5"
meta-oe
meta-multimedia
meta-python
meta-networking = "work:a06c29be2f5bc204f965ee07298c34232c5c39fc"
meta-riscv = "work:3048b416520d3607bbe3909002175f952c40e1a4"
Initialising tasks: 100% |############################################################################################################| Time: 0:00:02
Sstate summary: Wanted 972 Found 0 Missed 972 Current 0 (0% match, 0% complete)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: core-image-full-cmdline-1.0-r0 do_rootfs: The postinstall intercept hook 'update_font_cache' failed, details in /home/pino/workspace/opensource_work/riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-image-full-cmdline/1.0-r0/temp/log.do_rootfs
ERROR: core-image-full-cmdline-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /home/pino/workspace/opensource_work/riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-image-full-cmdline/1.0-r0/temp/log.do_rootfs.19363
ERROR: Task (/home/pino/workspace/opensource_work/riscv-yocto/openembedded-core/meta/recipes-extended/images/core-image-full-cmdline.bb:do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2885 tasks of which 5 didn't need to be rerun and 1 failed.
Summary: 1 task failed:
/home/pino/workspace/opensource_work/riscv-yocto/openembedded-core/meta/recipes-extended/images/core-image-full-cmdline.bb:do_rootfs
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
from meta-riscv.
@pino-kim ok thanks you are on latest thats good. I dont use ubuntu 16.04 but I will see if I can get hold of a box with ubuntu 16.04 and reproduce it. meanwhile can you post content of
/home/pino/workspace/opensource_work/riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-image-full-cmdline/1.0-r0/temp/log.do_rootfs
from meta-riscv.
log_do_rootfs.txt
@kraj
what's your distro linux???
I want to check differ yours and ubuntu 16.04.
I hope to see shell run. : - )
from meta-riscv.
Related Issues (20)
- current go-cross cannot support cgo for riscv64
- go_1.19.4.bb not install standard lib code HOT 1
- Qemu RISCV64 build fails due to nfs-utils HOT 11
- Kernel modules will not work on MangoPi pro HOT 2
- Where is recipes-bsp/boot0/boot0.bb? HOT 3
- BrokenPipeError: [Errno 32] Broken pipe HOT 4
- opensbi: do_install() fails for visionfive2 HOT 2
- visionfive2 missing ChipsMedia_VisionFive2 license file
- weston does not start on Visionfive2 HOT 3
- glibc build failed on ARCH riscv32 HOT 3
- build failing on start with 'ERROR: Nothing RPROVIDES 'systemd'' HOT 2
- Milk-V Duo: Kernel compilation fails HOT 1
- mangopi-mq-pro u-boot-allwinnerd1-1_1.0-r0 do_fetch HOT 1
- visionfive 2 cpu0: cpufreq_init: failed to get clk and cpufreq-dt: failed register driver: -19 HOT 4
- Error while compiling perf HOT 1
- No hdmi on mangopi HOT 3
- [master: visionfive2] mesa-pvr HOT 4
- How can I increase my RAM memory for milk-v duo 64MB? HOT 1
- star64 - u-boot compilation fails
- visionfive2-pvr-graphics: failing installation with SysV init
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from meta-riscv.