From: Christoph Hellwig <hch@lst.de>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Christoph Hellwig <hch@lst.de>,
Brian Cain <bcain@codeaurora.org>,
Sid Manning <sidneym@codeaurora.org>,
linux-hexagon@vger.kernel.org, linux-kernel@vger.kernel.org,
Nick Desaulniers <ndesaulniers@google.com>,
clang-built-linux@googlegroups.com
Subject: Re: how can we test the hexagon port in mainline
Date: Wed, 7 Jul 2021 16:10:54 +0200 [thread overview]
Message-ID: <20210707141054.GA24828@lst.de> (raw)
In-Reply-To: <YNQE0YJzC2xmWg+2@Ryzen-9-3900X.localdomain>
On Wed, Jun 23, 2021 at 09:06:41PM -0700, Nathan Chancellor wrote:
> On Wed, Jun 23, 2021 at 05:35:38PM +0200, Arnd Bergmann wrote:
> > On Wed, Jun 23, 2021 at 5:17 PM Christoph Hellwig <hch@lst.de> wrote:
> > >
> > > It seem like it still isn't complete enought for a kernel build, though:
> > >
> > > $ export CROSS_COMPILE=/opt/clang+llvm-12.0.0-cross-hexagon-unknown-linux-musl/x86_64-linux-gnu/bin/hexagon-unknown-linux-musl-
> > > $ make ARCH=hexagon LLVM=1 oldconfig
> > > ...
> > > scripts/Kconfig.include:40: linker 'ld.lld' not found
> >
> > I tried this using the prebuilt binaries from apt.llvm.org:
> >
> > $ make ARCH=hexagon LLVM=1 O=obj-hexagon CROSS_COMPILE=hexagon-linux-
> > LLVM_IAS=1 CC=llvm-12 defconfig modules vmlinux
> > <stdin>:1515:2: warning: syscall clone3 not implemented [-W#warnings]
> > #warning syscall clone3 not implemented
> > ^
> > 1 warning generated.
> >
> > Doing the same thing with allmodconfig results in an internal error
> > with clang-12
> > while compiling kernel/locking/lockdep.c. Same thing with clang-13.
> > After turning
> > off lock debugging, it seems fine.
>
> I've reported this upstream with you on CC:
>
> https://bugs.llvm.org/show_bug.cgi?id=50838
I've not actually got any mail from that Cc..
> Christoph, that toolchain should work (I had to install libtinfo5 and
> libc++1-7 on Debian Buster):
>
> $ export PATH=$HOME/tmp/clang+llvm-12.0.0-cross-hexagon-unknown-linux-musl/x86_64-linux-gnu/bin:$PATH
>
> $ make -skj"$(nproc)" ARCH=hexagon CROSS_COMPILE=hexagon-unknown-linux-musl LLVM=1 LLVM_IAS=1 defconfig all
hch@brick:~/work/linux$ make -j4 ARCH=hexagon
CROSS_COMPILE=hexagon-unknown-linux-musl LLVM=1 LLVM_IAS=1 defconfig all
HOSTCC scripts/basic/fixdep
clang: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
next prev parent reply other threads:[~2021-07-07 14:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 14:18 how can we test the hexagon port in mainline Christoph Hellwig
2021-06-23 14:39 ` Brian Cain
2021-06-23 14:53 ` Arnd Bergmann
2021-06-23 15:15 ` Brian Cain
2021-06-23 15:17 ` 'Christoph Hellwig'
2021-06-23 15:35 ` Arnd Bergmann
2021-06-24 4:06 ` Nathan Chancellor
2021-07-07 14:10 ` Christoph Hellwig [this message]
2021-07-07 17:42 ` Nathan Chancellor
2021-07-08 5:27 ` Christoph Hellwig
2021-07-08 17:54 ` Nick Desaulniers
2021-07-08 18:35 ` Brian Cain
2021-07-08 19:08 ` Nick Desaulniers
2021-06-23 15:10 ` 'Christoph Hellwig'
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=20210707141054.GA24828@lst.de \
--to=hch@lst.de \
--cc=arnd@arndb.de \
--cc=bcain@codeaurora.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=sidneym@codeaurora.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).