mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Jiri Slaby <jirislaby@kernel.org>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	linux-parisc@vger.kernel.org,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: hppa vDSO and compiler (non-)support
Date: Tue, 8 Mar 2022 15:51:41 +0100	[thread overview]
Message-ID: <2e1f3e41-7097-e68d-d312-9319ad62565c@gmx.de> (raw)
In-Reply-To: <d2713ae1-0ca5-9e5a-b7d2-b7d0f1f5614a@kernel.org>

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?
Would it make sense to add the detection for SUSE too?

> 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'm currently installing opensuse to try myself though...

> So could vDSO be optional on hppa via KConfig?
The vDSO is one of the first things which is built during kernel build process.
This is why you fail.
Making it optional doesn't make sense, because then the kernel wouldn't be able
to start the user space processes.

> I used to use the cross compiler to at least compile-check the following  tty drivers:
> arch/parisc/kernel/pdc_cons.o
> drivers/tty/serial/mux.o
> drivers/tty/serial/8250/8250_gsc.o

I assume you never built a full kernel, but stopped when building those modules?
Without libgcc.a the kernel itself wouldn't have linked before either.

Helge

  reply	other threads:[~2022-03-08 14:52 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 [this message]
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

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=2e1f3e41-7097-e68d-d312-9319ad62565c@gmx.de \
    --to=deller@gmx.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.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®