| Summary: | [2.5 M1 RC3] Build Appliance : failed to build core-image-sato image & build-appliance-image | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Runtime | Reporter: | nagarajagopal <nagarajagopalx.velu> | ||||
| Component: | build-appliance | Assignee: | Richard Purdie <richard.purdie> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | Medium | CC: | ee.peng.yeoh, richard.purdie | ||||
| Version: | 2.5 | ||||||
| Target Milestone: | 2.5 | ||||||
| Hardware: | x86 | ||||||
| OS: | x86_64 | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | Yes (doc changes required) | |||||
| Attachments: |
|
||||||
Hi, This looks like you're using master and its failing to build binutils for the target. I have some questions: * Does this same failure occur if you rerun the build from scratch (i.e. does it reproduce?) * Does "bitbake binutils" instead of build-appliance work? * Which version of Ubuntu are you using? * Which MACHINE setting are you using? * Which commit from master are you using? Below find details,
- same failure occured and closed the console automatically during the build from scratch.
- "bitbake binutils" build successfully.
- Ubuntu 16.04 and x86_64
- MACHINE = "qemux86"
- Master commit b9dcab772fd37ed8376a87d3194195e13ff52d10
QA 2.5_M1.rc3 commit f2b03953b28755277437641645669396f285919a
used autobuilder image to boot yocto build appliance in VMWare,
Download autobuilder from below link,
https://autobuilder.yocto.io/pub/releases/yocto-2.5_M1.rc3/build-appliance/
I tried autobuiler yocto build appliance image and compiled yocto build appliance image in Linux environment with commit id f2b03953b28755277437641645669396f285919a.
Both are failed to build core-image-sato and build-appliance-image.
VMWare memory and disk size after booted yocto build appliance,
run below command in VMWare,
$ df -h
Filesystem size used Avail Use% Mounted on
/dev/root 54G 1.8G 49G 4% /
devtmpfs 2.0G 76K 2.0G 1% /dev
tmpfs 2.0G 3.1G 2.0G 1% /run
tmpfs 2.0G 272K 2.0G 1% /var/volatile
/dev/sda1 23M 7.0M 16M 31% /boot
$ free -m
total used free shared buff/cache available
Mem: 3938 336 3486 3 115 3540
Swap: 0 0 0
I understand the problem now, thanks. We don't really support running builds in 4GB ram, could you increase the memory to the VM? I increased RAM memory to 6GB in VMWare, now build-appliance-image is build succesfully. Thanks. I believe the question has been answered. Please comment a new question of you still needinfo. Was fixed by increasing memory size, resolving. |
Created attachment 4179 [details] Failed log file core-image-minimal is compiling successfully in VMWare on Ubuntu. When building the build-appliance-image in VMWare on Ubuntu, getting below error, {standard input}:169902: Error: unknown pseudo-op: `.lbb11' {standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive i586-poky-linux-g++: internal compiler error: Killed This is related to memory issue.