From: Helge Deller <deller@gmx.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "Jiri Slaby" <jirislaby@kernel.org>,
linux-parisc@vger.kernel.org,
"Linux kernel mailing list" <linux-kernel@vger.kernel.org>,
"Martin Liška" <mliska@suse.cz>,
"Andreas Schwab" <schwab@linux-m68k.org>
Subject: Re: hppa vDSO and compiler (non-)support
Date: Thu, 24 Mar 2022 08:20:25 +0100 [thread overview]
Message-ID: <af596db9-07c7-ca6a-46f6-546e9f39e471@gmx.de> (raw)
In-Reply-To: <11063f42-6d3c-64d2-f3ed-9593be469fa5@roeck-us.net>
On 3/22/22 18:50, Guenter Roeck wrote:
>>>>> Building parisc64:generic-64bit_defconfig ... failed
>>>>> --------------
>>>>> Error log:
>>>>> arch/parisc/kernel/vdso64/Makefile:30: FORCE prerequisite is missing
>>>>> arch/parisc/kernel/vdso32/sigtramp.S: Assembler messages:
>>>>> arch/parisc/kernel/vdso32/sigtramp.S:39: Error: unknown pseudo-op: `.proc'
>>>>> ...
>>>>> arch/parisc/kernel/vdso32/restart_syscall.S:32: Error: .cfi_endproc without corresponding .cfi_startproc
>>>>> make[2]: *** [arch/parisc/kernel/vdso32/Makefile:34: arch/parisc/kernel/vdso32/restart_syscall.o] Error 1
>>>>> make[2]: *** Waiting for unfinished jobs....
>>>>> make[2]: *** [arch/parisc/kernel/vdso32/Makefile:34: arch/parisc/kernel/vdso32/sigtramp.o] Error 1
>>>>> make[1]: *** [arch/parisc/Makefile:177: vdso_prepare] Error 2
>>>>> make: *** [Makefile:219: __sub-make] Error 2
To recap - the solution was to add CROSS32_COMPILE=hppa-linux- , e.g.:
make ARCH=parisc CROSS_COMPILE=hppa64-linux- CROSS32_COMPILE=hppa-linux-
The better solution (for kernel >= v5.17) is to simply leave out the CROSS_COMPILE/CROSS32_COMPILE
parameters and let the Makefile autodetect everything:
make ARCH=parisc -> 32bit kernel
make ARCH=parisc64 -> 64bit kernel
It's now documented in the Wiki:
https://parisc.wiki.kernel.org/index.php/Cross_compiler_toolchain#How_to_build_the_kernel
Helge
prev parent reply other threads:[~2022-03-24 7:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 11:06 Jiri Slaby
2022-03-08 14:51 ` Helge Deller
2022-03-08 16:40 ` Helge Deller
2022-03-09 5:48 ` Jiri Slaby
2022-03-21 7:26 ` Jiri Slaby
2022-03-21 18:51 ` Helge Deller
2022-03-22 9:19 ` Jiri Slaby
2022-03-22 9:42 ` Helge Deller
2022-03-22 13:05 ` Guenter Roeck
2022-03-22 14:25 ` Helge Deller
2022-03-22 15:19 ` Guenter Roeck
2022-03-22 16:16 ` Helge Deller
2022-03-22 17:50 ` Guenter Roeck
2022-03-24 7:20 ` Helge Deller [this message]
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=af596db9-07c7-ca6a-46f6-546e9f39e471@gmx.de \
--to=deller@gmx.de \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mliska@suse.cz \
--cc=schwab@linux-m68k.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®