Dear Koen and Khem,
               I have the patch for libpostproc error.Can any of you guide
me how to apply the patch and go with the build.
    I am stranderd here.


Thanks and Regards,
Gibson

On Thu, Mar 19, 2015 at 11:36 PM, Gibson Justian <guitargib...@gmail.com>
wrote:

> Hi  Khem,
>      So how do I apply the patch?? Googled it not much of info apparently.
>
> Is it right to open the particular path and edit the file and append
> libpostproc and proceed with the build?
>
> Regards,
> Gibson
>
> On Thu, Mar 19, 2015 at 11:23 PM, Khem Raj <raj.k...@gmail.com> wrote:
>
>>
>> > On Mar 19, 2015, at 6:50 PM, Gibson Justian <guitargib...@gmail.com>
>> wrote:
>> >
>> > Hi  Koen and Khem ,
>> >               I was building the Angstrom linux for beaglebone black. I
>> > have been trying to build it for couple of months.
>> >
>> > I tried couple of times with 64-bit machine with Debian 7.8 and Centos
>> > ======>  failed.
>> > I tried with a 32 bit machine with Debian 7.8 =========================>
>> > failed
>> > Actually fails in the libpostproc and opencv
>> >
>> ---------------------------------------------------------------------------------------------------------------------------------------
>> > Below are the console output.
>> >
>> ---------------------------------------------------------------------------------------------------------------------------------------
>> > configure: set WARNING_CFLAGS to  -Wall -Wdeclaration-after-statement
>> > -Wvla -Wpointer-arith -Wmissing-declarations -Wmissing-prototypes
>> > -Wredundant-decls -Wundef -Wwrite-strings -Wformat-nonliteral
>> > -Wformat-security -Wold-style-definition -Winit-self
>> -Wmissing-include-dirs
>> > -Waddress -Waggregate-return -Wno-multichar -Wnested-externs
>> > | configure: set ERROR_CFLAGS to
>> > | checking for BZ2_bzlibVersion in -lbz2... yes
>> > | checking bzlib.h usability... yes
>> > | checking bzlib.h presence... yes
>> > | checking for bzlib.h... yes
>> > | checking for FFMPEG... yes
>> > | checking for POSTPROC... configure: error: Package requirements
>> > (libpostproc libavcodec libavutil) were not met:
>> > |
>> > | No package 'libpostproc’ found
>>
>> you need something like
>>
>> http://lists.openembedded.org/pipermail/openembedded-core/2014-December/099751.html
>>
>> > |
>> > | Consider adjusting the PKG_CONFIG_PATH environment variable if you
>> > | installed software in a non-standard prefix.
>> > |
>> > | Alternatively, you may set the environment variables POSTPROC_CFLAGS
>> > | and POSTPROC_LIBS to avoid the need to call pkg-config.
>> > | See the pkg-config man page for more details.
>> > |
>> > | Configure failed. The contents of all config.log files follows to aid
>> > debugging
>> > | ERROR: oe_runconf failed
>> > | WARNING: exit code 1 from a shell command.
>> > | ERROR: Function failed: do_configure (log file is located at
>> >
>> /home/gibson/setup-scripts/build/tmp-angstrom_v2014_12-glibc/work/armv7at2hf-vfp-neon-angstrom-linux-gnueabi/gst-ffmpeg/0.10.13-r8/temp/log.do_configure.10569)
>> > ERROR: Task 6080
>> >
>> (/home/gibson/setup-scripts/sources/openembedded-core/meta/recipes-multimedia/gstreamer/
>> > gst-ffmpeg_0.10.13.bb, do_configure) failed with exit code '1'
>> > Currently 1 running tasks (6333 of 7983):
>> > 0: opencv-2.4.9+gitAUTOINC+df8e28283f-r0 do_fetch (pid 28032)
>> >
>> >
>> >
>> >
>> >
>> >
>> > --
>> > Regards,
>> > Gibson.J
>> > _______________________________________________
>> > Angstrom-distro-devel mailing list
>> > Angstrom-distro-devel@linuxtogo.org
>> >
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
>>
>>
>> _______________________________________________
>> Angstrom-distro-devel mailing list
>> Angstrom-distro-devel@linuxtogo.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
>>
>
>
>
> --
> Regards,
> Gibson.J
>



-- 
Regards,
Gibson.J
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Reply via email to