public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: 'Christoph Hellwig' <hch@lst.de>
To: Brian Cain <bcain@codeaurora.org>
Cc: 'Arnd Bergmann' <arnd@arndb.de>, 'Christoph Hellwig' <hch@lst.de>,
	'Sid Manning' <sidneym@codeaurora.org>,
	"'open list:QUALCOMM HEXAGON...'" <linux-hexagon@vger.kernel.org>,
	'Linux Kernel Mailing List' <linux-kernel@vger.kernel.org>
Subject: Re: how can we test the hexagon port in mainline
Date: Wed, 23 Jun 2021 17:17:46 +0200	[thread overview]
Message-ID: <20210623151746.GA4247@lst.de> (raw)
In-Reply-To: <08e101d76842$94f78a60$bee69f20$@codeaurora.org>

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
make[1]: *** [scripts/kconfig/Makefile:77: oldconfig] Error 1
make: *** [Makefile:614: oldconfig] Error 2


  reply	other threads:[~2021-06-23 15:17 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' [this message]
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
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=20210623151746.GA4247@lst.de \
    --to=hch@lst.de \
    --cc=arnd@arndb.de \
    --cc=bcain@codeaurora.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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