From: Guenter Roeck <linux@roeck-us.net>
To: Helge Deller <deller@gmx.de>
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 06:05:16 -0700 [thread overview]
Message-ID: <20220322130516.GA724287@roeck-us.net> (raw)
In-Reply-To: <812d4a38-8cb1-a7be-c504-87d095aea883@gmx.de>
On Tue, Mar 22, 2022 at 10:42:33AM +0100, Helge Deller wrote:
> On 3/22/22 10:19, Jiri Slaby wrote:
> > Hello,
> >
> > On 21. 03. 22, 19:51, Helge Deller wrote:
> >> * Jiri Slaby <jirislaby@kernel.org>:
> >>> On 09. 03. 22, 6:48, Jiri Slaby wrote:
> >>>> On 08. 03. 22, 15:51, Helge Deller wrote:
> >>>>> On 3/8/22 12:06, Jiri Slaby wrote:
> >>>>>> since the "parisc: Add vDSO support" commit, I can no longer
> >>>>>> cross-build a hppa kernel. I see two issues:
> >>>>>>
> >>>>>> 1) CROSS32_COMPILE detection doesn't work here, as openSUSE
> >>>>>> provides hppa-suse-linux-* binaries. It's easy to overcome by
> >>>>>> "CROSS32_COMPILE=hppa-suse-linux-"
> >>>>>
> >>>> ...
> >>>>> Would it make sense to add the detection for SUSE too?
> >>>
> >>> So, could 1) be fixed on the Kconfig side? Or should I (people running SUSE)
> >>> use "CROSS32_COMPILE=hppa-suse-linux-"?
> >>
> >> Could you please try if this patch fixes it for you?
> >
> > Works like a charm:
> > $ make V=1 O=../a/arch/parisc/ ARCH=parisc -j6 drivers/tty/serial/mux.o
> > ...
> >> hppa-suse-linux-gcc <flags deleted> -o drivers/tty/serial/mux.o /home/latest/linux/drivers/tty/serial/mux.c
> >> if hppa-suse-linux-objdump -h drivers/tty/serial/mux.o | ...; fi
> >
> > Thanks.
>
> Great!
> I've queued up a patch in for-next...
>
Does that also fix the build problems now seen in mainline ?
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/sigtramp.S:40: Error: unknown pseudo-op: `.callinfo'
arch/parisc/kernel/vdso32/sigtramp.S:41: Error: unknown pseudo-op: `.entry'
arch/parisc/kernel/vdso32/sigtramp.S:44: Error: no such instruction: `ldi 0,%r25'
arch/parisc/kernel/vdso32/sigtramp.S:45: Error: no such instruction: `ldi 173,%r20'
arch/parisc/kernel/vdso32/sigtramp.S:46: Error: no such instruction: `ble 0x100(%sr2,%r0)'
arch/parisc/kernel/vdso32/sigtramp.S:49: Error: no such instruction: `ldi 1,%r25'
arch/parisc/kernel/vdso32/sigtramp.S:50: Error: no such instruction: `ldi 173,%r20'
arch/parisc/kernel/vdso32/sigtramp.S:51: Error: no such instruction: `ble 0x100(%sr2,%r0)'
arch/parisc/kernel/vdso32/sigtramp.S:54: Error: unknown pseudo-op: `.exit'
arch/parisc/kernel/vdso32/sigtramp.S:55: Error: unknown pseudo-op: `.procend'
arch/parisc/kernel/vdso32/sigtramp.S:76: Error: unknown pseudo-op: `.stringz'
arch/parisc/kernel/vdso32/restart_syscall.S: Assembler messages:
arch/parisc/kernel/vdso32/restart_syscall.S:16: Error: bad or irreducible absolute expression
arch/parisc/kernel/vdso32/restart_syscall.S:16: Error: junk at end of line, first unrecognized character is `:'
arch/parisc/kernel/vdso32/restart_syscall.S:26: Error: no such instruction: `ldw 0(%sp),%r31'
arch/parisc/kernel/vdso32/restart_syscall.S:29: Error: no such instruction: `be 0x100(%sr2,%r0)'
arch/parisc/kernel/vdso32/restart_syscall.S:30: Error: no such instruction: `ldi 0,%r20'
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.
Thanks,
Guenter
next prev parent reply other threads:[~2022-03-22 13:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 11:06 hppa vDSO and compiler (non-)support 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 [this message]
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
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=20220322130516.GA724287@roeck-us.net \
--to=linux@roeck-us.net \
--cc=deller@gmx.de \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--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