All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: clang-built-linux <llvm@lists.linux.dev>,
	Arnd Bergmann <arnd@kernel.org>
Subject: Re: help with clang build for mips
Date: Fri, 22 Jul 2022 14:29:01 +0100	[thread overview]
Message-ID: <CADVatmNtFYyqk0KwYzB1x6hOPkQ=0gV8mPN1BWp6QWrCs5GaxA@mail.gmail.com> (raw)
In-Reply-To: <YtBMNLXEQ4WVJezu@dev-arch.thelio-3990X>

On Thu, Jul 14, 2022 at 6:02 PM Nathan Chancellor <nathan@kernel.org> wrote:
>
> Hi Sudip,
>
> On Thu, Jul 14, 2022 at 05:39:39PM +0100, Sudip Mukherjee wrote:
> > Hi All,
> >
> > I am trying to build the kernel for mips architecture with clang. I
> > see some of the configuration builds properly, but some of the configs
> > fails with the error (fuloong2e_defconfig):
> >

<snip>

>
> Unfortunately, I doubt there is much interest in that work, given MIPS
> as an architecture isn't being developed anymore. Might be an
> interesting hobbyist project though. It is probably best to just test
> configurations that work and make sure that those do not regress. Others
> are more than welcome to weigh in though!

So, I have now disabled those builds with unsupported CPU. But I do
see some others with linux-next and will like to have your feedback on
them please.

mips clang cavium_octeon_defconfig:

clang-15: error: unsupported argument '-mfix-cn63xxp1' to option '-Wa,'
make[1]: *** [scripts/Makefile.build:250: scripts/mod/empty.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1290: prepare0] Error 2

+++++++++++++++++++++++++++++++++++++

mips clang decstation_64_defconfig:

arch/mips/Makefile:281: *** CONFIG_CPU_DADDI_WORKAROUNDS unsupported
without -msym32.  Stop.

+++++++++++++++++++++++++++++++++++++

mips clang ip28_defconfig:

clang-15: error: unknown argument: '-mr10k-cache-barrier=store'
clang-15: error: unknown argument: '-mr10k-cache-barrier=store'
make[1]: *** [scripts/Makefile.build:118: kernel/bounds.s] Error 1
make: *** [arch/mips/Makefile:407: archprepare] Error 2

+++++++++++++++++++++++++++++++++++++

mips clang loongson2k_defconfig:

error: ABI 'o32' is not supported on CPU 'mips64r2'
make[1]: *** [Kbuild:48: missing-syscalls] Error 1
make: *** [arch/mips/Makefile:409: archprepare] Error 2

+++++++++++++++++++++++++++++++++++++

mips clang loongson3_defconfig:

error: ABI 'o32' is not supported on CPU 'mips64r2'
make[1]: *** [Kbuild:48: missing-syscalls] Error 1
make: *** [arch/mips/Makefile:409: archprepare] Error 2

+++++++++++++++++++++++++++++++++++++



-- 
Regards
Sudip

  parent reply	other threads:[~2022-07-22 13:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14 16:39 help with clang build for mips Sudip Mukherjee
2022-07-14 17:02 ` Nathan Chancellor
2022-07-14 20:11   ` Arnd Bergmann
2022-07-15  9:59     ` Sudip Mukherjee
2022-07-15 10:30       ` Arnd Bergmann
2022-07-22 13:29   ` Sudip Mukherjee [this message]
2022-07-22 15:21     ` Nathan Chancellor
2022-07-24  8:24       ` Sudip Mukherjee
2022-07-24 14:49       ` Arnd Bergmann
2022-07-25 16:02         ` Nathan Chancellor
2022-07-25 19:38           ` Arnd Bergmann

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='CADVatmNtFYyqk0KwYzB1x6hOPkQ=0gV8mPN1BWp6QWrCs5GaxA@mail.gmail.com' \
    --to=sudipm.mukherjee@gmail.com \
    --cc=arnd@kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@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.