From: Nathan Chancellor <nathan@kernel.org>
To: Christoph Hellwig <hch@lst.de>, Brian Cain <bcain@codeaurora.org>,
Sid Manning <sidneym@codeaurora.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
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 10:42:27 -0700 [thread overview]
Message-ID: <1ee8fc44-3e8c-91c0-7909-a636757dbda4@kernel.org> (raw)
In-Reply-To: <20210707141054.GA24828@lst.de>
Hi Christoph,
On 7/7/2021 7:10 AM, Christoph Hellwig wrote:
> On Wed, Jun 23, 2021 at 09:06:41PM -0700, Nathan Chancellor wrote:
>> 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..
Sorry, I directed that at Arnd. I should have kept you in the loop too.
>> 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
Hmmm, is that with libtinfo5 installed (or whatever the ncurses-compat
equivalent is on your distribution installed)? I had that problem on
Debian until I insta
Brian/Sid, it might be worth flipping LLVM_ENABLE_TERMINFO to OFF during
your cmake configuration so that there are less dynamic dependencies and
it is easier for more people to run the toolchain. Android's clang team
did the same thing:
https://github.com/android/ndk/issues/574
With https://reviews.llvm.org/D42055, there should not be too much of a
sacrifice.
Cheers,
Nathan
next prev parent reply other threads:[~2021-07-07 17:42 UTC|newest]
Thread overview: 16+ 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: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
2021-07-07 17:42 ` Nathan Chancellor [this message]
2021-07-08 5:27 ` Christoph Hellwig
2021-07-08 17:54 ` Nick Desaulniers
2021-07-08 18:35 ` Brian Cain
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=1ee8fc44-3e8c-91c0-7909-a636757dbda4@kernel.org \
--to=nathan@kernel.org \
--cc=arnd@arndb.de \
--cc=bcain@codeaurora.org \
--cc=clang-built-linux@googlegroups.com \
--cc=hch@lst.de \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.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 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.