Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v1] libv4l: build utils only on MMU (with fork support) platforms
Date: Sat, 22 Jul 2017 21:44:25 +0200	[thread overview]
Message-ID: <20170722214425.5c9ab5a8@windsurf> (raw)
In-Reply-To: <41bd7a05-4254-e7e4-7846-ed5e4d99d0ad@st.com>

Hello,

On Tue, 18 Jul 2017 09:08:18 +0000, Hugues FRUCHET wrote:

> Back to your exact build issue, the best fix on my opinion is to add a 
> dependency on fork() symbol in configure.ac instead of the one proposed 
> in libv4l.mk, find attached a patch proposal.

Does your patch actually work? A lot of the utils in utils/ do require
the libraries, won't they fail to build if the libraries are not built ?

Could you make a clean patch submission to resolve this issue ?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-07-22 19:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11 17:26 [Buildroot] [RFC v1] libv4l: build utils only on MMU (with fork support) platforms Peter Seiderer
2017-07-11 21:13 ` Thomas Petazzoni
2017-07-17 10:07 ` Hugues FRUCHET
2017-07-17 18:09   ` Peter Seiderer
2017-07-18  9:08     ` Hugues FRUCHET
2017-07-22 19:44       ` Thomas Petazzoni [this message]
2017-07-24  8:14         ` Hugues FRUCHET
2017-07-22 21:36       ` Peter Seiderer
2017-07-24  8:08         ` Hugues FRUCHET
2017-07-24 17:38           ` Peter Seiderer
2017-07-24 17:51             ` Peter Seiderer
2017-07-25  7:54               ` Hugues FRUCHET

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=20170722214425.5c9ab5a8@windsurf \
    --to=thomas.petazzoni@free-electrons.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