Send Motion-user mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: Motion on CentOS (Mr Dave)
2. Re: New Motion Release Status (Mr Dave)
3. Re: New Motion Release Status (Frank W. Samuelson)
4. Re: Motion on CentOS (tosiara)
----------------------------------------------------------------------
Message: 1
Date: Sat, 17 Oct 2015 16:24:06 -0600
From: Mr Dave <[email protected]>
Subject: Re: [Motion-user] Motion on CentOS
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"
Try running
./configure --with-ffmpeg=/root/ffmpeg_build
The message is indicating that it can not find the ffmpeg libraries that
you built so you need to manually point configure to that location with
the use of the configure flag.
Dave
On 10/17/2015 2:58 PM, Ole Andreas Gl?ersen wrote:
> It looks like I now have a comlete ffmpeg comilation.
>
> [root@localhost ~]# ls -ltr /root/ffmpeg_build/
> totalt 20
> drwxr-xr-x. 2 root root 17 okt. 17 21:02 bin
> -rw-r--r--. 1 root root 6804 okt. 17 21:27 ffmpeg.sh
> -rw-r--r--. 1 root root 1028 okt. 17 21:28 ffmpeg2.sh
> drwxr-xr-x. 6 root root 53 okt. 17 22:14 share
> drwxr-xr-x. 3 root root 4096 okt. 17 22:14 lib
> drwxr-xr-x. 16 root root 4096 okt. 17 22:14 include
>
>
> When I try to install motion (from Mr-Dave by git download) I got this:
>
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking minix/config.h usability... no
> checking minix/config.h presence... no
> checking for minix/config.h... no
> checking whether it is safe to define __EXTENSIONS__... yes
> checking for gcc... (cached) gcc
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ISO C89... (cached) none needed
> checking for Darwin... no
> checking for *BSD... no
> checking for gcc... (cached) gcc
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ISO C89... (cached) none needed
> checking threads... yes
> checking for sdl... no
> checking for libjpeg-turbo... skipping
> checking for libjpeg-mmx... skipping
> checking for jpeg_set_defaults in -ljpeg... yes
> checking for pkg-config... /bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for FFMPEG... no
> configure: error: Package requirements (libavutil libavformat
> libavcodec libswscale) were not met:
>
> No package 'libavutil' found
> No package 'libavformat' found
> No package 'libavcodec' found
> No package 'libswscale' found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables FFMPEG_CFLAGS
> and FFMPEG_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>
>
> No of those can be installed by yum on CentOS.
>
> My script (runned as root):
>
> #!/bin/bash
> cd ~/ffmpeg_sources
> git clone https://github.com/Mr-Dave/motion.git
> cd motion
> autoreconf -fiv
> ./configure
> make
> make install
> ldconfig
>
>
>
> Any tip?
>
>
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Sat, 17 Oct 2015 16:37:38 -0600
From: Mr Dave <[email protected]>
Subject: Re: [Motion-user] New Motion Release Status
To: Ximin Luo <[email protected]>, Motion discussion list
<[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
All:
We are going to try again to get a new official release. The discussion
of the release will be on the motion-devel user list.
Dave
On 10/14/2015 6:36 PM, Mr Dave wrote:
> I have not heard anything back on this.
>
> If the code in my repo is selected for the basis of a new release,
> I'll follow the approach that you've indicated within the git repo and
> whatever is needed or desired for the SVN. And of course as indicated
> in the original email, attempt to address whatever else is needed from
> a checklist, documentation, tar balls, RPMs, debs, wiki, platform
> testing standpoint. My time to be able to work on these activities
> however is rapidly ending however since I can normally only work on
> the Motion project in the Aug-Nov timeframe of each year.
>
> Dave
>
> On 10/14/2015 5:52 PM, Ximin Luo wrote:
>> On 21/08/15 04:05, Mr Dave wrote:
>>> Ken,
>>>
>>> Is there anything that I (or others if they so desire) can do to
>>> assist in getting a new release moved forward? Documentation, wiki,
>>> code, manual, change log, checklist, etc?
>>>
>>> Dave
>> Hi,
>>
>> Any news on this? Please CC me in future replies as I am not on the
>> mailing list.
>>
>> I see from the archives that there was talk about adding in
>> multithreading. Please, no; that is off-topic for this thread and
>> adding new features is an extremely bad thing to do *for release
>> purposes*.
>>
>> Good software engineering would be to
>>
>> a) make a separate branch for the release. and forbid major new
>> functionality here
>> b) make bug fixes for the release there
>> c) release a bunch of "candidates" for testing
>> d) do the release
>>
>> Any bug fixes done on this branch can be merged/rebased back onto the
>> master branch later.
>>
>> X
>>
>
------------------------------
Message: 3
Date: Sat, 17 Oct 2015 19:45:57 -0400 (EDT)
From: "Frank W. Samuelson" <[email protected]>
Subject: Re: [Motion-user] New Motion Release Status
To: Motion discussion list <[email protected]>
Message-ID:
<alpine.lrh.2.20.1510171942310.22...@pool-108-18-138-241.washdc.fios.verizon.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Yay!
Thanks, Mr. Dave!
An official release will mean that people can just grab
motion with RTSP from their distribution repositories, and
we will have fewer compile problems.
On Sat, 17 Oct 2015, Mr Dave wrote:
> All:
>
> We are going to try again to get a new official release. The discussion
> of the release will be on the motion-devel user list.
>
> Dave
> On 10/14/2015 6:36 PM, Mr Dave wrote:
>> I have not heard anything back on this.
>>
>> If the code in my repo is selected for the basis of a new release,
>> I'll follow the approach that you've indicated within the git repo and
>> whatever is needed or desired for the SVN. And of course as indicated
>> in the original email, attempt to address whatever else is needed from
>> a checklist, documentation, tar balls, RPMs, debs, wiki, platform
>> testing standpoint. My time to be able to work on these activities
>> however is rapidly ending however since I can normally only work on
>> the Motion project in the Aug-Nov timeframe of each year.
>>
>> Dave
>>
>> On 10/14/2015 5:52 PM, Ximin Luo wrote:
>>> On 21/08/15 04:05, Mr Dave wrote:
>>>> Ken,
>>>>
>>>> Is there anything that I (or others if they so desire) can do to
>>>> assist in getting a new release moved forward? Documentation, wiki,
>>>> code, manual, change log, checklist, etc?
>>>>
>>>> Dave
>>> Hi,
>>>
>>> Any news on this? Please CC me in future replies as I am not on the
>>> mailing list.
>>>
>>> I see from the archives that there was talk about adding in
>>> multithreading. Please, no; that is off-topic for this thread and
>>> adding new features is an extremely bad thing to do *for release
>>> purposes*.
>>>
>>> Good software engineering would be to
>>>
>>> a) make a separate branch for the release. and forbid major new
>>> functionality here
>>> b) make bug fixes for the release there
>>> c) release a bunch of "candidates" for testing
>>> d) do the release
>>>
>>> Any bug fixes done on this branch can be merged/rebased back onto the
>>> master branch later.
>>>
>>> X
>>>
>>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>
>
------------------------------
Message: 4
Date: Sun, 18 Oct 2015 08:42:08 +0300
From: tosiara <[email protected]>
Subject: Re: [Motion-user] Motion on CentOS
To: Motion discussion list <[email protected]>
Message-ID:
<CACHTdwSYeSaeSCYCBQ=hdzejr2brmn_7fijimw7xytrjbct...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
can you try compiling ffmpeg, but don't install it? Just specify prefix to
be in the source dir. Then, specify motion to use that dir to search for
libs
http://www.lavrsen.dk/foswiki/bin/view/Motion/FrequentlyAskedQuestions#Compile_ffmpeg_from_sources
On Sat, Oct 17, 2015 at 11:58 PM, Ole Andreas Gl?ersen <
[email protected]> wrote:
> It looks like I now have a comlete ffmpeg comilation.
>
> [root@localhost ~]# ls -ltr /root/ffmpeg_build/
> totalt 20
> drwxr-xr-x. 2 root root 17 okt. 17 21:02 bin
> -rw-r--r--. 1 root root 6804 okt. 17 21:27 ffmpeg.sh
> -rw-r--r--. 1 root root 1028 okt. 17 21:28 ffmpeg2.sh
> drwxr-xr-x. 6 root root 53 okt. 17 22:14 share
> drwxr-xr-x. 3 root root 4096 okt. 17 22:14 lib
> drwxr-xr-x. 16 root root 4096 okt. 17 22:14 include
>
>
> When I try to install motion (from Mr-Dave by git download) I got this:
>
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking minix/config.h usability... no
> checking minix/config.h presence... no
> checking for minix/config.h... no
> checking whether it is safe to define __EXTENSIONS__... yes
> checking for gcc... (cached) gcc
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ISO C89... (cached) none needed
> checking for Darwin... no
> checking for *BSD... no
> checking for gcc... (cached) gcc
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ISO C89... (cached) none needed
> checking threads... yes
> checking for sdl... no
> checking for libjpeg-turbo... skipping
> checking for libjpeg-mmx... skipping
> checking for jpeg_set_defaults in -ljpeg... yes
> checking for pkg-config... /bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for FFMPEG... no
> configure: error: Package requirements (libavutil libavformat libavcodec
> libswscale) were not met:
>
> No package 'libavutil' found
> No package 'libavformat' found
> No package 'libavcodec' found
> No package 'libswscale' found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables FFMPEG_CFLAGS
> and FFMPEG_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>
>
> No of those can be installed by yum on CentOS.
>
>
> My script (runned as root):
>
> #!/bin/bash
> cd ~/ffmpeg_sources
> git clone https://github.com/Mr-Dave/motion.git
> cd motion
> autoreconf -fiv
> ./configure
> make
> make install
> ldconfig
>
>
>
> Any tip?
>
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------------------------------------------------------
------------------------------
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
End of Motion-user Digest, Vol 113, Issue 6
*******************************************
