All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Subject: hppa vDSO and compiler (non-)support
Date: Tue, 8 Mar 2022 12:06:55 +0100	[thread overview]
Message-ID: <d2713ae1-0ca5-9e5a-b7d2-b7d0f1f5614a@kernel.org> (raw)

Hi,

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-"

2) openSUSE doesn't provide any libc for hppa. So gcc doesn't provide 
libgcc.a and the build of vDSO fails.

So could vDSO be optional on hppa via KConfig?

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

thanks,
-- 
js
suse labs

             reply	other threads:[~2022-03-08 11:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 11:06 Jiri Slaby [this message]
2022-03-08 14:51 ` hppa vDSO and compiler (non-)support 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

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=d2713ae1-0ca5-9e5a-b7d2-b7d0f1f5614a@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 \
    /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.