From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Question regarding rootfile warning "Error! '/aarch64' in rootfiles files found!"
Date: Sun, 05 Dec 2021 11:47:47 +0100 [thread overview]
Message-ID: <e33ab2c5-2333-c368-46c6-4e17668f3d9e@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
Hello *,
while preparing Core Update 163, these messages are emitted at the end of a build on my workstation:
> Error! '/aarch64' in rootfiles files found!
> ./config/rootfiles/common/liburcu:#usr/include/urcu/arch/aarch64.h
> ./config/rootfiles/common/liburcu:#usr/include/urcu/uatomic/aarch64.h
> ./config/rootfiles/common/gdb:#usr/share/gdb/syscalls/aarch64-linux.xml
> Replace by xxxMACHINExxx !
While I get the intention of a check like this, these appear to be safe to ignore. However, I'd like
to have someone more experienced on this to confirm that opinion.
Thanks, and best regards,
Peter Müller
next reply other threads:[~2021-12-05 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 10:47 Peter Müller [this message]
2021-12-05 11:45 ` Adolf Belka
2021-12-09 19:31 ` Peter Müller
2021-12-09 19:39 ` Peter Müller
2021-12-09 19:41 ` Michael Tremer
2021-12-09 19:52 ` Peter Müller
2021-12-09 19:54 ` Michael Tremer
2021-12-15 14:06 ` Adolf Belka
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=e33ab2c5-2333-c368-46c6-4e17668f3d9e@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.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