From: Joseph Kogut <joseph.kogut@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 1/4] llvm: disable bindings on host
Date: Sat, 19 Oct 2019 23:55:51 -0700 [thread overview]
Message-ID: <CAMWSM7hm-fKZRyZo65=Tg5Z_H+cu_+Xge0=mjnGMvLSjoUrjLg@mail.gmail.com> (raw)
In-Reply-To: <0f630437-4501-2ff6-dae1-f7178e5e91cb@mind.be>
On Sat, Oct 19, 2019 at 3:47 PM Arnout Vandecappelle <arnout@mind.be> wrote:
>
>
>
> On 24/07/2019 19:35, Joseph Kogut wrote:
> > Signed-off-by: Joseph Kogut <joseph.kogut@gmail.com>
>
> Can you explain why this is needed/wanted?
>
> Regards,
> Arnout
>
Nope. This commit was a while ago, and when I was working on this
feature, I found that certain bindings were still enabled which caused
a build failure. I researched the configure flags for LLVM, and found
this one. Enabling it fixed the build, so I added it.
It's very possible the enabling of this flag obviates the need for the
priors. If that's the case, I would of course support removing the
unneeded flags.
Best,
Joseph
next prev parent reply other threads:[~2019-10-20 6:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 17:35 [Buildroot] [RFC PATCH 0/4] Add Buildroot toolchain support for LLD Joseph Kogut
2019-07-24 17:35 ` [Buildroot] [RFC PATCH 1/4] llvm: disable bindings on host Joseph Kogut
2019-08-01 10:11 ` Romain Naour
2019-10-19 22:47 ` Arnout Vandecappelle
2019-10-20 6:55 ` Joseph Kogut [this message]
2019-07-24 17:35 ` [Buildroot] [RFC PATCH 2/4] package/lld: new package Joseph Kogut
2019-10-19 22:48 ` Arnout Vandecappelle
2019-07-24 17:35 ` [Buildroot] [RFC PATCH 3/4] toolchain-wrapper: add linker override option Joseph Kogut
2019-10-19 22:49 ` Arnout Vandecappelle
2019-07-24 17:35 ` [Buildroot] [RFC PATCH 4/4] Add linker override to config options Joseph Kogut
2019-07-27 2:25 ` Carlos Santos
2019-07-29 17:55 ` Joseph Kogut
2019-10-19 23:01 ` Arnout Vandecappelle
2019-08-01 13:13 ` [Buildroot] [RFC PATCH 0/4] Add Buildroot toolchain support for LLD 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='CAMWSM7hm-fKZRyZo65=Tg5Z_H+cu_+Xge0=mjnGMvLSjoUrjLg@mail.gmail.com' \
--to=joseph.kogut@gmail.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 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.