From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Doug Anderson <dianders@chromium.org>,
Anatoly Pugachev <matorola@gmail.com>
Cc: Sparc kernel list <sparclinux@vger.kernel.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Daniel Thompson <daniel.thompson@linaro.org>
Subject: Re: [sparc64] unable to build kernel after bbfceba15f8 / "kdb: Get rid of confusing diag msg from "rd" if current task has no regs"
Date: Fri, 7 Feb 2020 11:58:05 +0100 [thread overview]
Message-ID: <ba1e277d-511c-9ed6-994c-d096e54c3ab3@physik.fu-berlin.de> (raw)
In-Reply-To: <CAD=FV=UYbMMr+obKqCvKpfpsJ-T5n6p9cZZsjFwF4kfTKM0Jqw@mail.gmail.com>
Hi Doug!
On 2/4/20 11:13 PM, Doug Anderson wrote:
> Argh. Sorry about this. :( I'm not setup with a sparc compiler, but
> I've simulated your results on arm64 by just commenting out the
> definition of "DBG_MAX_REG_NUM" in "arch/arm64/include/asm/kgdb.h".
At least on Debian and openSUSE, compilers for most kernel architectures
are available as cross-compilers ready for installation. So it might
be a good idea to have a machine running Debian or openSUSE around
for performing these tests.
On Debian, you can just install a SPARC compiler with:
$ apt install gcc-sparc64-linux-gnu
The only target that is currently missing is ia64 but that's on my
TODO list for Debian :).
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
prev parent reply other threads:[~2020-02-07 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 21:14 [sparc64] unable to build kernel after bbfceba15f8 / "kdb: Get rid of confusing diag msg from "rd" if current task has no regs" Anatoly Pugachev
2020-02-04 22:13 ` Doug Anderson
2020-02-05 9:41 ` Anatoly Pugachev
2020-02-05 15:51 ` Daniel Thompson
2020-02-07 10:58 ` John Paul Adrian Glaubitz [this message]
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=ba1e277d-511c-9ed6-994c-d096e54c3ab3@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matorola@gmail.com \
--cc=sparclinux@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;
as well as URLs for NNTP newsgroup(s).