From: Pavel Machek <pavel@ucw.cz>
To: robh@kernel.org, kernel list <linux-kernel@vger.kernel.org>
Subject: compile error in scripts/dtc/libfdt/fdt.c
Date: Sun, 14 Mar 2021 23:45:03 +0100 [thread overview]
Message-ID: <20210314224503.GA2000@duo.ucw.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
Hi!
I get failure building ARM kernel. I can workaround it with. Are
system fdt headers used, or something like that?
I failed to copy the error message, but FDT_ERR_ALIGNMENT was
undefined symbol.
This is on 5.12-rc3.
BR,
Pavel
diff --git a/scripts/dtc/libfdt/fdt.c b/scripts/dtc/libfdt/fdt.c
index 3e893073da05..d15f437567d9 100644
--- a/scripts/dtc/libfdt/fdt.c
+++ b/scripts/dtc/libfdt/fdt.c
@@ -24,7 +24,7 @@ int32_t fdt_ro_probe_(const void *fdt)
/* The device tree must be at an 8-byte aligned address */
if ((uintptr_t)fdt & 7)
- return -FDT_ERR_ALIGNMENT;
+ return -FDT_ERR_INTERNAL;
if (fdt_magic(fdt) == FDT_MAGIC) {
/* Complete tree */
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2021-03-14 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 22:45 Pavel Machek [this message]
2021-03-22 20:34 ` compile error in scripts/dtc/libfdt/fdt.c Rob Herring
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=20210314224503.GA2000@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.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