From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Mark Brown <broonie@kernel.org>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Bug Report] selftests: arm64: build errors
Date: Tue, 4 Jun 2024 13:13:45 +0500 [thread overview]
Message-ID: <8e1e2f1d-a578-43c0-ad55-fb593967ac5e@collabora.com> (raw)
In-Reply-To: <7b7f4dd1-bc13-4827-84d6-20ebed7119b6@sirena.org.uk>
On 6/3/24 6:31 PM, Mark Brown wrote:
> On Mon, Jun 03, 2024 at 06:28:16PM +0500, Muhammad Usama Anjum wrote:
>
>> gcc pac.c /pauth/pac_corruptor.o /pauth/helper.o -o /pauth/pac -Wall -O2 -g
>> -I/linux_mainline/tools/testing/selftests/ -I/linux_mainline/tools/include
>> -mbranch-protection=pac-ret -march=armv8.2-a
>> In file included from pac.c:13:
>> ../../kselftest_harness.h: In function ‘clone3_vfork’:
>> ../../kselftest_harness.h:88:9: error: variable ‘args’ has initializer but
>> incomplete type
>> 88 | struct clone_args args = {
>
> This is in the generic code.
>
>> CC check_prctl
>> check_prctl.c: In function ‘set_tagged_addr_ctrl’:
>> check_prctl.c:19:14: error: ‘PR_SET_TAGGED_ADDR_CTRL’ undeclared (first use
>> in this function)
>> 19 | ret = prctl(PR_SET_TAGGED_ADDR_CTRL, val, 0, 0, 0);
>>
>> gcc -mbranch-protection=standard -DBTI=1 -ffreestanding -Wall -Wextra -Wall
>> -O2 -g -I/linux_mainline/tools/testing/selftests/
>> -I/linux_mainline/tools/include -c -o /bti/test-bti.o test.c
>> test.c: In function ‘handler’:
>> test.c:85:50: error: ‘PSR_BTYPE_MASK’ undeclared (first use in this
>> function); did you mean ‘PSR_MODE_MASK’?
>> 85 | write(1, &"00011011"[((uc->uc_mcontext.pstate & PSR_BTYPE_MASK)
>
>> I've GCC 8 installed. I'm not expecting the errors because of a little
>> older compiler. Any more ideas about the failures?
>
> You need to run headers_install IIRC.
I'm running:
make headers && make -C tools/testing/selftests
I've tried gcc 12 as well.
--
BR,
Muhammad Usama Anjum
next prev parent reply other threads:[~2024-06-04 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 13:28 Muhammad Usama Anjum
2024-06-03 13:31 ` Mark Brown
2024-06-04 8:13 ` Muhammad Usama Anjum [this message]
2024-06-05 20:48 ` Mark Brown
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=8e1e2f1d-a578-43c0-ad55-fb593967ac5e@collabora.com \
--to=usama.anjum@collabora.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=will@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
all inboxes | Powered by JetHome®