From: Jiri Slaby <jirislaby@kernel.org>
To: "Helge Deller" <deller@gmx.de>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
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: Mon, 21 Mar 2022 08:26:47 +0100 [thread overview]
Message-ID: <dd4e55aa-0b3e-6e18-7ec2-3bec02cafde0@kernel.org> (raw)
In-Reply-To: <d2a09bf3-9bd3-588a-99a1-598281d08678@kernel.org>
On 09. 03. 22, 6:48, Jiri Slaby wrote:
> Hi,
>
> On 08. 03. 22, 15:51, Helge Deller wrote:
>> Hi Jiri,
>>
>> Thanks for testing on parisc!
>>
>> 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-"
>>
>> How is it handled for other platforms like s390x?
>
> s390 simply uses CC for vdso32:
> cmd_vdso32cc = $(CC) $(c_flags) -c -o $@ $<
>
>> Would it make sense to add the detection for SUSE too?
>
> Maybe.
So, could 1) be fixed on the Kconfig side? Or should I (people running
SUSE) use "CROSS32_COMPILE=hppa-suse-linux-"?
>>> 2) openSUSE doesn't provide any libc for hppa. So gcc doesn't provide
>>> libgcc.a and the build of vDSO fails.
>>
>> libgcc.a comes with the compiler, I don't think you need libc for that.
>
> I was told glibc is needed to build libgcc.a.
2) was fixed on the compiler (SUSE) side. cross-hppa-gcc12-bootstrap was
introduced -- note it's known to be a misnomer -- it should have been
like s/-bootstrap/-baremetal/.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2022-03-21 7:26 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 [this message]
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
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=dd4e55aa-0b3e-6e18-7ec2-3bec02cafde0@kernel.org \
--to=jirislaby@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=deller@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.