From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Upgrading LLVM and Clang to version 11.0.0... issue with libclc
Date: Fri, 8 Jan 2021 11:07:59 +0100 [thread overview]
Message-ID: <148a6a55-99e4-e4f1-252c-17c693f5df57@bootlin.com> (raw)
In-Reply-To: <0a47a156-bcde-41a3-bd34-24df0549d0ba@gmail.com>
Hi Romain,
Many thanks for your help and insights!
On 1/7/21 6:41 PM, Romain Naour wrote:
> I believe CMake try to check clang as cross-compiler before using it.
> Can you share the CMake error log file ?
Here are the contents of the CMakeError.log file:
>>>
Determining if the CLC compiler works failed with the following output:
Determining if the CLC compiler works failed with the following output:
Determining if the CLC compiler works failed with the following output:
Determining if the CLC compiler works failed with the following output:
<<<
CMakeOutput.log is a bit too big to share here
>
> For now, host/bin/clang can't be used as cross-compiler to build application
> (the simple test program) because we need to add a wrapper like for gcc.
>
> configure.py was kind enough to accept host/bin/clang as is to build libclc library.
>
> If we can skip the cmake test, the library should build as before.
Ok, I'll try.
> I don't think we have to build libclc before clang, as you can see in the
> current packaging only mesa3d depends on libclc. Clang itself doesn't depend on
> libclc.
>
> You can find some details about the initial work in this blog:
> https://www.linuxembedded.fr/2018/07/llvmclang-integration-into-buildroot/
Great! This will definitely be useful.
Many thanks,
Michael.
--
Michael Opdenacker, CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-01-08 10:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 16:59 [Buildroot] Upgrading LLVM and Clang to version 11.0.0... issue with libclc Michael Opdenacker
2021-01-07 17:41 ` Romain Naour
2021-01-08 10:07 ` Michael Opdenacker [this message]
2021-01-08 11:13 ` Romain Naour
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=148a6a55-99e4-e4f1-252c-17c693f5df57@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=buildroot@busybox.net \
/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