From: Peter Seiderer <ps.report@gmx.net>
To: Sean Young <sean@mess.org>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH v4l-utils] Add missing linux/bpf_common.h
Date: Fri, 9 Nov 2018 22:22:40 +0100 [thread overview]
Message-ID: <20181109222240.74c3bc22@gmx.net> (raw)
In-Reply-To: <20181109121038.al23ts654c6vwwbl@gofer.mess.org>
Hello Sean,
On Fri, 9 Nov 2018 12:10:38 +0000, Sean Young <sean@mess.org> wrote:
> Hi Peter,
>
> On Thu, Nov 08, 2018 at 10:13:38PM +0100, Peter Seiderer wrote:
> > Thanks, works for the buildroot use case (disabling
> > bpf support unconditionally)...
> >
> > The reason to provide copies of the linux kernel headers in v4l-utils
> > is to be independent of old(-er) headers provided by toolchains?
> >
> > If so a copy of bpf_common.h is still needed (and the fallback, for
> > out of linux kernel usage, define for __NR_bpf in bpf.h enhanced for
> > all supported archs)?
>
> I have seen this problem on debian 7. Why do we care about compiling
> on something that ancient?
It is not about compiling on what system, it is about which toolchain
is used (for cross-compile), and the initial failure comes from
the buildroot [1] embedded system autobuild tests...
Personally I do not care about these toolchains (but the buildroot
people think it is worth to do automatic build tests with them) and
can live with the disabling of the bpf support....
Regards,
Peter
[1] https://buildroot.org/
>
>
> Sean
next prev parent reply other threads:[~2018-11-10 7:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 20:30 [PATCH v4l-utils] Add missing linux/bpf_common.h Peter Seiderer
2018-11-06 10:38 ` Sean Young
2018-11-06 21:43 ` Peter Seiderer
2018-11-07 12:05 ` Sean Young
2018-11-08 21:13 ` Peter Seiderer
2018-11-09 12:10 ` Sean Young
2018-11-09 21:22 ` Peter Seiderer [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-06 22:20 Peter Seiderer
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=20181109222240.74c3bc22@gmx.net \
--to=ps.report@gmx.net \
--cc=linux-media@vger.kernel.org \
--cc=sean@mess.org \
/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.