From: Robert Cochran <yocto@mindchasers.com>
To: meta-freescale@lists.yoctoproject.org
Subject: [meta-qoriq] qoriq-atf has at least two problems in master branch...
Date: Sun, 20 Nov 2022 08:05:03 -0500 [thread overview]
Message-ID: <fe1875a3-c8b8-0a89-d2a1-f65c1cd31852@mindchasers.com> (raw)
Hello,
Using master branches, I was trying to build a core-image-minimal with
MACHINE="ls1046afrwy", but it fails at qoriq-atf:
ERROR: qoriq-atf-2.4-r0 do_compile: oe_runmake failed
First problem: u-boot.bin-tfa could not be found in
/build/yocto/bld_ls1046afrwy/tmp/deploy/images/ls1046afrwy
| Makefile:1128: ***
'BL33=/build/yocto/bld_ls1046afrwy/tmp/deploy/images/ls1046afrwy/u-boot.bin-tfa'
was specified, but
'/build/yocto/bld_ls1046afrwy/tmp/deploy/images/ls1046afrwy/u-boot.bin-tfa'
does not exist. Stop.
I was able to work around this by copying u-boot.bin-tfa from
/build/yocto/bld_ls1046afrwy/tmp/work/ls1046afrwy-poky-linux/u-boot-qoriq/2021.04+fslgit-r0/image/boot
Second problem: "bl2/bl2.elf has a LOAD segment with RWX permissions".
At this point, I don't know how to work around or patch this one.
| aarch64-poky-linux-ld.bfd: warning:
/build/yocto/bld_ls1046afrwy/tmp/work/ls1046afrwy-poky-linux/qoriq-atf/2.4-r0/git/build/ls1046afrwy/release/bl2/bl2.elf
has a LOAD segment with RWX permissions
| make: *** [Makefile:1089:
/build/yocto/bld_ls1046afrwy/tmp/work/ls1046afrwy-poky-linux/qoriq-atf/2.4-r0/git/build/ls1046afrwy/release/bl2/bl2.elf]
Error 1
| make: *** Waiting for unfinished jobs....
| aarch64-poky-linux-ld.bfd: warning:
/build/yocto/bld_ls1046afrwy/tmp/work/ls1046afrwy-poky-linux/qoriq-atf/2.4-r0/git/build/ls1046afrwy/release/bl31/bl31.elf
has a LOAD segment with RWX permissions
| make: *** [Makefile:1105:
/build/yocto/bld_ls1046afrwy/tmp/work/ls1046afrwy-poky-linux/qoriq-atf/2.4-r0/git/build/ls1046afrwy/release/bl31/bl31.elf]
Error 1
| ERROR: oe_runmake failed
| WARNING:
/build/yocto/bld_ls1046afrwy/tmp/work/ls1046afrwy-poky-linux/qoriq-atf/2.4-r0/temp/run.do_compile.16653:253
exit 1 from 'exit 1'
| WARNING: Backtrace (BB generated script):
| #1: bbfatal_log,
/build/yocto/bld_ls1046afrwy/tmp/work/ls1046afrwy-poky-linux/qoriq-atf/2.4-r0/temp/run.do_compile.16653,
line 253
| #2: die,
/build/yocto/bld_ls1046afrwy/tmp/work/ls1046afrwy-poky-linux/qoriq-atf/2.4-r0/temp/run.do_compile.16653,
line 237
| #3: oe_runmake,
/build/yocto/bld_ls1046afrwy/tmp/work/ls1046afrwy-poky-linux/qoriq-atf/2.4-r0/temp/run.do_compile.16653,
line 232
| #4: do_compile,
/build/yocto/bld_ls1046afrwy/tmp/work/ls1046afrwy-poky-linux/qoriq-atf/2.4-r0/temp/run.do_compile.16653,
line 191
| #5: main,
/build/yocto/bld_ls1046afrwy/tmp/work/ls1046afrwy-poky-linux/qoriq-atf/2.4-r0/temp/run.do_compile.16653,
line 266
ERROR: Task
(/build/yocto/meta-freescale/recipes-bsp/atf/qoriq-atf_2.4.bb:do_compile)
failed with exit code '1'
next reply other threads:[~2022-11-20 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 13:05 Robert Cochran [this message]
2022-11-20 14:59 ` [meta-freescale] [meta-qoriq] qoriq-atf has at least two problems in master branch Otavio Salvador
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=fe1875a3-c8b8-0a89-d2a1-f65c1cd31852@mindchasers.com \
--to=yocto@mindchasers.com \
--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 NNTP newsgroup(s).