From: Heiko Schocher <hs@denx.de>
To: meta-freescale@lists.yoctoproject.org
Cc: Chunrong Guo <chunrong.guo@nxp.com>, Ting Liu <ting.liu@nxp.com>,
Otavio Salvador <otavio@ossystems.com.br>
Subject: mpc854x support in master
Date: Wed, 9 Mar 2022 08:37:17 +0100 [thread overview]
Message-ID: <aa496596-e3a2-85bb-29cf-4128c8dca978@denx.de> (raw)
Hi all,
I just tried to build u-boot for machine p1020rdb with current master branches
$ bitbake u-boot
Loading cache: 100% |
| ETA: --:--:--
Loaded 0 entries from dependency cache.
Parsing recipes: 100%
|########################################################################################################################################################|
Time: 0:00:19
Parsing of 2535 .bb files complete (0 cached, 2535 parsed). 3927 targets, 491 skipped, 0 masked, 0
errors.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.53.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "ubuntu-18.04"
TARGET_SYS = "powerpc-poky-linux"
MACHINE = "p1020rdb"
DISTRO = "poky"
DISTRO_VERSION = "3.4+snapshot-8d0e8ee0da0c670b073ef844682275e9668b2bb9"
TUNE_FEATURES = "m32 ppce500v2 bigendian"
TARGET_FPU = ""
meta-freescale = "master:3c344467b28bc6e256755c8bf45f306fee70ea02"
meta-networking
meta-oe
meta-python = "master:912b3475a35fa414f51a22c1e088c39a164c2857"
meta
meta-poky
meta-yocto-bsp = "master:8d0e8ee0da0c670b073ef844682275e9668b2bb9"
and this fails with Error:
ERROR: libgcc-initial-11.2.0-r0 do_compile: oe_runmake failed
ERROR: libgcc-initial-11.2.0-r0 do_compile:
ExecutionError('/work/big/hs/temp/abb/build/tmp/work/ppce500v2-poky-linux/libgcc-initial/11.2.0-r0/temp/run.do_compile.46030',
1, None, None)
ERROR: Logfile of failure stored in:
/work/big/hs/temp/abb/build/tmp/work/ppce500v2-poky-linux/libgcc-initial/11.2.0-r0/temp/log.do_compile.46030
Log data follows:
[...]
/../../../../work-shared/gcc-11.2.0-r0/gcc-11.2.0/libgcc/../include -o crtendS.o -MT crtendS.o -MD
-MP -MF crtendS.dep -msdata=none -O2 -fno-asynchronous-unwind-tables -fPIC -c
../../../../../../../work-shared/gcc-11.2.0-r0/gcc-11.2.0/libgcc/crtstuff.c -DCRT_END -DCRTSTUFFS_O
| make: *** [../../../../../../../work-shared/gcc-11.2.0-r0/gcc-11.2.0/libgcc/static-object.mk:17:
unwind-c.o] Error 1
| make: *** Waiting for unfinished jobs....
| {standard input}: Assembler messages:
| {standard input}:108: Error: unrecognized opcode: `isel'
| {standard input}:111: Error: unrecognized opcode: `isel'
| {standard input}:472: Error: unrecognized opcode: `isel'
| {standard input}: Assembler messages:
| {standard input}:745: Error: unrecognized opcode: `isel'
| {standard input}:3809: Error: unrecognized opcode: `isel'
| make: *** [../../../../../../../work-shared/gcc-11.2.0-r0/gcc-11.2.0/libgcc/static-object.mk:17:
unwind-dw2-fde-dip.o] Error 1
| {standard input}:2683: Error: unrecognized opcode: `isel'
| {standard input}:2698: Error: unrecognized opcode: `isel'
| {standard input}:2717: Error: unrecognized opcode: `isel'
| {standard input}:2732: Error: unrecognized opcode: `isel'
| {standard input}:2851: Error: unrecognized opcode: `isel'
| {standard input}:2869: Error: unrecognized opcode: `isel'
| {standard input}:3590: Error: unrecognized opcode: `isel'
| {standard input}:3755: Error: unrecognized opcode: `isel'
| {standard input}:8368: Error: unrecognized opcode: `isel'
| make: *** [../../../../../../../work-shared/gcc-11.2.0-r0/gcc-11.2.0/libgcc/static-object.mk:17:
unwind-dw2.o] Error 1
| ERROR: oe_runmake failed
Compiling this with "dunfell" checkout meta layers works fine,
may as dunfell uses gcc9.3.0 ?
Are mpc854x builds supported with master, or are they deprecated?
May I miss some layer?
Thanks for any hints!
bye,
Heiko
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-52 Fax: +49-8142-66989-80 Email: hs@denx.de
reply other threads:[~2022-03-09 7:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aa496596-e3a2-85bb-29cf-4128c8dca978@denx.de \
--to=hs@denx.de \
--cc=chunrong.guo@nxp.com \
--cc=meta-freescale@lists.yoctoproject.org \
--cc=otavio@ossystems.com.br \
--cc=ting.liu@nxp.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).