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: Tue, 22 Mar 2022 17:16:32 +0100 [thread overview]
Message-ID: <4d52b78d-ed39-102f-ba64-3ba9c17f58f9@gmx.de> (raw)
In-Reply-To: <78abe69b-7914-1b38-c94e-7143f61f4909@roeck-us.net>
On 3/22/22 16:19, Guenter Roeck wrote:
> On 3/22/22 07:25, Helge Deller wrote:
>> On 3/22/22 14:05, Guenter Roeck wrote:
>>> Does that also fix the build problems now seen in mainline ?
>>
>> No.
>>
>>> 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
>>>
>>> This is with hppa64-linux-gcc (GCC) 11.2.0.
>>
>> Can you check if you have the 32-bit compiler (hppa-linux-gcc) installed too?
>> The errors above happen when building the 32-bit vDSO, for which you need the 32-bit compiler.
>>
>
> Yes, I do, but that doesn't help much if I want to build a 64-bit target such
> as generic-64bit_defconfig. Am I missing something ?
The 64-bit PA-RISC kernel now includes a built-in a 32-bit and a 64-bit vDSO for userspace.
To build the 32-bit vDSO (vdso32) you need the 32-bit hppa compiler installed.
That's what's being done above - see the path: arch/parisc/kernel/vdso32/
Can you try "make V=1" to see the command line?
Helge
next prev parent reply other threads:[~2022-03-22 16:16 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 [this message]
2022-03-22 17:50 ` Guenter Roeck
2022-03-24 7:20 ` Helge Deller
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=4d52b78d-ed39-102f-ba64-3ba9c17f58f9@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®