[Bug 762528] New: Failed to autogen.sh for gstreamer-vaapi in 1.6.0 in customize location

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=762528

            Bug ID: 762528
           Summary: Failed to autogen.sh for gstreamer-vaapi in 1.6.0 in
                    customize location
    Classification: Platform
           Product: GStreamer
           Version: 1.6.0
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gstreamer-vaapi
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: siew.hoon.lim at intel.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
                CC: bsreerenj at gmail.com, vjaquez at igalia.com
     GNOME version: ---

Having issue in run autogen.sh build issue in 1.6.0 version in build system for
customize location.

First do environment setting for build need to export:
export LD_LIBRARY_PATH=/home/test/opt/lib
export PKG_CONFIG_PATH=/home/test
/opt/lib/pkgconfig:/home/test/opt/share/pkgconfig
export PATH=/home/test/opt/bin:$PATH
export ACLOCAL_PATH=/home/test/opt/share/aclocal
export ACLOCAL="aclocal -I $ACLOCAL_PATH"

Install gstreamer, gst-plugins-base, gst-plugins-good 1.6.3 version
1. ./autogen.sh --prefix=/home/test/opt
2. make 
3. make install

git clone download the gstreamer-vaapi.
git checkout 1.6 

[test at slim50-desk gstreamer-vaapi]$ ./autogen.sh --prefix=/home/test/opt
+ passing argument --prefix=/home/test/opt to configure
+ options passed to configure:  --prefix=/home/test/opt
+ check for build tools
  checking for autoreconf ...
/usr/bin/autoreconf
  checking for pkg-config ...
/usr/bin/pkg-config
aclocal: error: couldn't open directory 'm4': No such file or directory
autoreconf: aclocal failed with exit status: 1

I don't have this kind of problem in previous old upstream master in 01.org
gstreamer-vaapi. Not able reproduce in gstreamer or gst-plugins-bad or
gst-plugins-base using same environment setting.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.