All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Kenton <skenton@ou.edu>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH  V2] mjpegtools: new package
Date: Mon, 02 Feb 2015 16:04:59 -0600	[thread overview]
Message-ID: <54CFF48B.1070506@ou.edu> (raw)
In-Reply-To: <20150202205339.GA4270@free.fr>

On 2/2/2015 2:53 PM, Yann E. MORIN wrote:
> Steve, All,
>
> On 2015-01-18 10:37 -0600, Steve Kenton spake thusly:
>> The mjpegtools programs are a set of tools
>> that can do recording of videos and playback,
>> simple cut-and-paste editing and the MPEG
>> compression of audio and video under Linux.
>>
>> http://mjpeg.sourceforge.net
>>
>> Signed-off-by Stephen M. Kenton<skenton@ou.edu>
> [--SNIP--]
>> diff -pruN buildroot.ori/package/mjpegtools/Config.in buildroot/package/mjpegtools/Config.in
>> --- buildroot.ori/package/mjpegtools/Config.in	1969-12-31 18:00:00.000000000 -0600
>> +++ buildroot/package/mjpegtools/Config.in	2015-01-16 11:05:54.949872151 -0600
>> @@ -0,0 +1,14 @@
>> +config BR2_PACKAGE_MJPEGTOOLS
>> +	bool "mjpegtools"
>> +	select BR2_PACKAGE_JPEG
>> +	depends on BR2_INSTALL_LIBSTDCPP
> I tried with this defconfig:
>      http://autobuild.buildroot.org/toolchains/configs/br-arm-full-nothread.config
>
> and just enabled mjpegtools above that, and it failed with:
>
>      In file included from picture.hh:27:0,
>                       from motionest.cc:61:
>      synchrolib.h:32:21: fatal error: pthread.h: No such file or directory
>       #include<pthread.h>
>                           ^
>      compilation terminated.
>
> So, it needs thread support.
>
OK, I'll look into it

Steve

      reply	other threads:[~2015-02-02 22:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-18 16:37 [Buildroot] [PATCH V2] mjpegtools: new package Steve Kenton
2015-02-02 20:53 ` Yann E. MORIN
2015-02-02 22:04   ` Steve Kenton [this message]

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=54CFF48B.1070506@ou.edu \
    --to=skenton@ou.edu \
    --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.