All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valentin Korenblit <valentinkorenblit@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] llvm: enable bpf
Date: Sat, 3 Nov 2018 15:24:26 +0100	[thread overview]
Message-ID: <f28fcd90-d01b-e62d-2fa0-1e1d4fb04473@gmail.com> (raw)
In-Reply-To: <CAPi7W801n8zqM-PLUF1RE5uShZ7+Xh9G2OkrnVEdZ3_Y3=bGpQ@mail.gmail.com>

Fabrice, Thomas,

> Dear Thomas,
> Le sam. 3 nov. 2018 ? 14:14, Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> a ?crit :
>> Hello,
>>
>> On Sat,  3 Nov 2018 13:27:56 +0100, Fabrice Fontaine wrote:
>>> BPF (in-kernel bytecode machine) is needed by libv4l
>>>
>>> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
>>> ---
>>>   package/llvm/llvm.mk | 3 +++
>>>   1 file changed, 3 insertions(+)
>>>
>>> diff --git a/package/llvm/llvm.mk b/package/llvm/llvm.mk
>>> index 1f9bd447f5..dae5d3f16d 100644
>>> --- a/package/llvm/llvm.mk
>>> +++ b/package/llvm/llvm.mk
>>> @@ -54,6 +54,9 @@ ifeq ($(BR2_PACKAGE_LLVM_AMDGPU),y)
>>>   LLVM_TARGETS_TO_BUILD += AMDGPU
>>>   endif
>>>
>>> +# Build BPF (in-kernel bytecode machine)
>>> +LLVM_TARGETS_TO_BUILD += BPF
>> Perhaps we should make this optional ? Or maybe the build time
>> difference is not that significant ?
> llvm and clang are already taking a long time to build on my "old"
> machine, I didn't notice a significant difference with or without BPF
> but I didn't measure it.

I think we should add a new option just like we did with AMDGPU backend
as we said we were only going to build backend for target archictecture
by default.

>> Best regards,
>>
>> Thomas
>> --
>> Thomas Petazzoni, CTO, Bootlin
>> Embedded Linux and Kernel engineering
>> https://bootlin.com
> Best Regards,
>
> Fabrice

Best regards,

Valentin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20181103/bf3d35b5/attachment.html>

  reply	other threads:[~2018-11-03 14:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-03 12:27 [Buildroot] [PATCH 1/4] llvm: fix build of host-llvm Fabrice Fontaine
2018-11-03 12:27 ` [Buildroot] [PATCH 2/4] llvm: enable bpf Fabrice Fontaine
2018-11-03 13:14   ` Thomas Petazzoni
2018-11-03 14:14     ` Fabrice Fontaine
2018-11-03 14:24       ` Valentin Korenblit [this message]
2018-11-03 14:45         ` Fabrice Fontaine
2018-11-03 12:27 ` [Buildroot] [PATCH 3/4] libv4l: add elfutils optional dependency Fabrice Fontaine
2018-11-03 13:18   ` Thomas Petazzoni
2018-11-03 14:06     ` Fabrice Fontaine
2018-11-03 12:27 ` [Buildroot] [PATCH 4/4] scripts/check-bin-arch: fix failure with bpf Fabrice Fontaine
2018-11-03 13:20   ` Thomas Petazzoni
2018-11-03 13:53     ` Fabrice Fontaine
2018-11-03 14:00       ` Thomas Petazzoni
2018-11-03 14:15 ` [Buildroot] [PATCH 1/4] llvm: fix build of host-llvm Romain Naour
2018-11-03 14:35   ` Thomas Petazzoni
2018-11-03 15:11     ` Fabrice Fontaine

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=f28fcd90-d01b-e62d-2fa0-1e1d4fb04473@gmail.com \
    --to=valentinkorenblit@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.