From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v6 2/4] package/libclc: new package
Date: Mon, 30 Apr 2018 10:02:56 +0200 [thread overview]
Message-ID: <20180430100256.74a03f09@windsurf> (raw)
In-Reply-To: <89066f3f-55f7-8d7e-8773-67221c027cea@smile.fr>
Hello,
On Mon, 30 Apr 2018 09:54:10 +0200, Valentin Korenblit wrote:
> >> diff --git a/package/libclc/Config.in b/package/libclc/Config.in
> >> new file mode 100644
> >> index 0000000000..a0f388c4e1
> >> --- /dev/null
> >> +++ b/package/libclc/Config.in
> >> @@ -0,0 +1,22 @@
> >> +config BR2_PACKAGE_LIBCLC
> >> + bool "libclc"
> >> + depends on BR2_PACKAGE_LLVM_ARCH_SUPPORTS
> >> + depends on BR2_HOST_GCC_AT_LEAST_4_8
> >> + depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_8
> >> + depends on BR2_TOOLCHAIN_HAS_THREADS
> >> + depends on BR2_INSTALL_LIBSTDCPP
> >> + depends on !BR2_TOOLCHAIN_HAS_GCC_BUG_64735 # std::shared_future
> >> + depends on !BR2_STATIC_LIBS
> >> + depends on BR2_USE_WCHAR # std::wstring
> > You seem to have replicated here all the dependencies of the target
> > LLVM package. However, you only depend on host-llvm and host-clang. Are
> > you sure all those dependencies are needed by libclc ?
>
> Actually, it wouldn't make sense to have libclc without target LLVM, but it
> is true that it is not a build dependency, so I'll remove them.
Is target LLVM a runtime dependency for libclc ? Could you explain a
bit the interaction between libclc and target LLVM, so that we can
decide what is the best way to express this dependency ?
> >> +# C++ compiler is used to build a small tool (prepare-builtins) for the host.
> >> +# It must be built with the C++ compiler from the host
> >> +LIBCLC_CONF_OPTS = --with-llvm-config=$(HOST_DIR)/usr/bin/llvm-config \
> >> + --prefix="/usr" \
> >> + --includedir="/usr/local/include" \
> > I'm not a big fan of /usr/local/include. Perhaps we should use
> > something really special like /usr/share/libclc/ or something like
> > this ?
>
> Perfect, I'll change it to that directory
Thanks!
> >> + --pkgconfigdir="/usr/lib/pkgconfig" \
> >> + --with-cxx-compiler=$(HOSTCXX)
> > Weird for a target package to use the host compiler, no ?
>
> Yes, it is used only in the target utils/prepare-builtins.o, all the
> other stuff is compiled with host-clang.
OK.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-04-30 8:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 16:14 [Buildroot] [PATCH v6 0/4] llvm for mesa3d Valentin Korenblit
2018-04-11 16:14 ` [Buildroot] [PATCH v6 1/4] package/clang: new package Valentin Korenblit
2018-04-28 12:51 ` Thomas Petazzoni
2018-04-30 7:20 ` Valentin Korenblit
2018-04-11 16:14 ` [Buildroot] [PATCH v6 2/4] package/libclc: " Valentin Korenblit
2018-04-28 13:06 ` Thomas Petazzoni
2018-04-30 7:54 ` Valentin Korenblit
2018-04-30 8:02 ` Thomas Petazzoni [this message]
2018-04-30 8:35 ` Valentin Korenblit
2018-04-11 16:14 ` [Buildroot] [PATCH v6 3/4] package/mesa3d: enable OpenCL support Valentin Korenblit
2018-04-11 16:14 ` [Buildroot] [PATCH v6 4/4] package/clinfo: new package Valentin Korenblit
2018-04-23 16:14 ` [Buildroot] [PATCH v6 0/4] llvm for mesa3d 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=20180430100256.74a03f09@windsurf \
--to=thomas.petazzoni@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