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: Tue, 11 Jul 2017 23:13:06 +0200 [thread overview]
Message-ID: <20170711231306.7405dea8@windsurf.lan> (raw)
In-Reply-To: <20170711172624.7516-1-ps.report@gmx.net>
Hello,
On Tue, 11 Jul 2017 19:26:24 +0200, Peter Seiderer wrote:
> Fixes [1]:
>
> CXXLD v4l2-compliance
> .../output/build/libv4l-1.12.5/lib/libv4lconvert/.libs/libv4lconvert.so: undefined reference to `fork'
> collect2: error: ld returned 1 exit status
>
> [1] http://autobuild.buildroot.net/results/7e8/7e8fbd99a8c091d7bbeedd16066297682bbe29fe
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
> The libv4l build for noMMU platforms was enabled with commit 'package/libv4l:
> allow build of v4l2 utilities on noMMU platforms' (see [2]). But libv4lconvert uses
> fork internally, so all utils linking against fail to build. Fix this by disabling
> the utils on noMMU platforms (so keep building all libraries).
>
> Alternatives would be:
>
> - disable libv4l on all noMMU platforms (not only the utils), revert a part
> of commit [2]
>
> - create a patch to disable only libv4lconvert (and all dependend utils)
> on noMMU platforms
>
> [2] https://git.buildroot.net/buildroot/commit/?id=f837251785e9389f53d695ddb8a094707865171b
Hugues, could you comment on this, since you originally re-enabled
libv4l for noMMU architectures ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-11 21:13 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 [this message]
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
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=20170711231306.7405dea8@windsurf.lan \
--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 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.