All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] scripts/check-bin-arch: fix failure with bpf
Date: Sat, 3 Nov 2018 15:00:33 +0100	[thread overview]
Message-ID: <20181103150033.1e4d78d2@windsurf> (raw)
In-Reply-To: <CAPi7W80r=y9NZseUxw31Mq_9nhPcRjK+AJrE_TbjvXUzGehnNw@mail.gmail.com>

Hello,

On Sat, 3 Nov 2018 14:53:48 +0100, Fabrice Fontaine wrote:

> I wasn't able to reproduce this "None" architecture issue.
> But I think it was "None" because the llvm/clang found on Peter's
> machine was very old (3.8):
> clang -idirafter /usr/local/include -idirafter
> /usr/lib/llvm-3.8/bin/../lib/clang/3.8.1/include -idirafter
> /usr/include/x86_64-linux-gnu -idirafter /usr/include
> -I../../../include -target bpf -O2 -c grundig.c
> 
> With my patch's serie, I'm building a host-clang in version 7.0 that
> supports BPF and in this case the architecture is correctly set to
> "Linux BPF".
> I tested with a clang in version 6.0 installed from Ubuntu 18.04
> repositories on my host machine and it was also "Linux BPF".

OK, but then you're not fixing the problem on Peter's machine: with
your patch series, if he doesn't enable BR2_PACKAGE_ELFUTILS, libv4l
configure script will still detect the system-wide clang/llvm
installed, which will produce those bogus "None" binaries.

Which is why there is a need to explicitly disable building the BPF
protocol support, except if we know that Buildroot is providing all the
necessary dependencies.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-11-03 14:00 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
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 [this message]
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=20181103150033.1e4d78d2@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 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.