Re: [yocto] [meta-raspberrypi3] Failed to build gstreamer1.0-plugins-bad with minimal configuration

2016-11-02 Thread Khem Raj
Can you test this patch here


https://github.com/kraj/meta-raspberrypi/commit/73be88cec27bb3b9d52d7782bd82c60395626abd.patch

and let me know if it fixes your issue ?


On Tue, Nov 1, 2016 at 11:51 AM, Karim ATIKI  wrote:
> Hi Paul,
>
>
> Thanks for your feedback.
>
> Unfortunately I was suspecting such a problem.
>
>
> Regarding the config below, is it possible to install the
> "dispmanx"component to activate EGL ?
>
>
> What recipe provides dispmanx ?
>
>
> Karim
>
>
>
>
>
> 
> De : Paul Barker 
> Envoyé : samedi 29 octobre 2016 23:13
> À : Karim ATIKI
> Cc : yocto
> Objet : Re: [yocto] [meta-raspberrypi3] Failed to build
> gstreamer1.0-plugins-bad with minimal configuration
>
> On Fri, 28 Oct 2016 05:56:07 +
> Karim ATIKI  wrote:
>
>> Hi Paul,
>>
>>
>> Thanks a lot for your feedback and analysis.
>>
>> I think it sohuld compile without X11 and Wayland as it's a very
>> common configuration
>>
>> for RaspberryPi being used with Qt5.x applications.
>>
>>
>> Do you think it's bug related to Gstreamer1.0 configuration ?
>>
>>
>>
>> Karim
>>
>
> The do_configure log for gstreamer1.0-plugins-bad does contain:
>
> configure: WARNING: X or Wayland is required for OpenGL support
>
> configure.ac in gst-plugins-bad-1.8.3 contains:
>
> dnl EGL
> if test "x$HAVE_EGL" = "xno"; then
>   if test "x$HAVE_GL" = "xno"; then
> AC_MSG_WARN([Building requires either EGL or GLX for OpenGL
> support])
>   fi
> else
>   if test "x$NEED_EGL" != "xno"; then
> if test "x$HAVE_WINDOW_WAYLAND" = "xyes" -o "x$HAVE_WINDOW_X11" =
> "xyes" -o "x$HAVE_WINDOW_DISPMANX" = "xyes"; then
>   GL_LIBS="$GL_LIBS -lEGL $EGL_LIBS"
>   GL_CFLAGS="$GL_CFLAGS $EGL_CFLAGS"
>   USE_EGL=yes
> fi
>   fi
> fi
> ;;
>
> In config.status EGL_LIBS contains "-lbcm_host -lvcos
> -lvchiq_arm", however GL_LIBS only contains "-lGLESv2". So I'd say
> EGL_LIBS is not being included in to GL_LIBS because
> HAVE_WINDOW_WAYLAND, HAVE_WINDOW_X11 and HAVE_WINDOW_DISPMAX are all
> false.
>
> GL_LIBS is used in gst-libs/gst/gl/Makefile.am so that's the variable
> the libraries should be listed in.
>
> I'd say that's an upstream issue - it really looks like it's demanding
> X or Wayland to be enabled for OpenGL to work. I'd suggest raising the
> issue upsteream.
>
> Thanks,
> Paul Barker
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi3] Failed to build gstreamer1.0-plugins-bad with minimal configuration

2016-11-01 Thread Karim ATIKI
Hi Paul,


Thanks for your feedback.

Unfortunately I was suspecting such a problem.


Regarding the config below, is it possible to install the "dispmanx"component 
to activate EGL ?


What recipe provides dispmanx ?


Karim





De : Paul Barker 
Envoyé : samedi 29 octobre 2016 23:13
À : Karim ATIKI
Cc : yocto
Objet : Re: [yocto] [meta-raspberrypi3] Failed to build 
gstreamer1.0-plugins-bad with minimal configuration

On Fri, 28 Oct 2016 05:56:07 +
Karim ATIKI  wrote:

> Hi Paul,
>
>
> Thanks a lot for your feedback and analysis.
>
> I think it sohuld compile without X11 and Wayland as it's a very
> common configuration
>
> for RaspberryPi being used with Qt5.x applications.
>
>
> Do you think it's bug related to Gstreamer1.0 configuration ?
>
>
>
> Karim
>

The do_configure log for gstreamer1.0-plugins-bad does contain:

configure: WARNING: X or Wayland is required for OpenGL support

configure.ac in gst-plugins-bad-1.8.3 contains:

dnl EGL
if test "x$HAVE_EGL" = "xno"; then
  if test "x$HAVE_GL" = "xno"; then
AC_MSG_WARN([Building requires either EGL or GLX for OpenGL support])
  fi
else
  if test "x$NEED_EGL" != "xno"; then
if test "x$HAVE_WINDOW_WAYLAND" = "xyes" -o "x$HAVE_WINDOW_X11" = 
"xyes" -o "x$HAVE_WINDOW_DISPMANX" = "xyes"; then
  GL_LIBS="$GL_LIBS -lEGL $EGL_LIBS"
  GL_CFLAGS="$GL_CFLAGS $EGL_CFLAGS"
  USE_EGL=yes
fi
  fi
fi
;;

In config.status EGL_LIBS contains "-lbcm_host -lvcos
-lvchiq_arm", however GL_LIBS only contains "-lGLESv2". So I'd say
EGL_LIBS is not being included in to GL_LIBS because
HAVE_WINDOW_WAYLAND, HAVE_WINDOW_X11 and HAVE_WINDOW_DISPMAX are all
false.

GL_LIBS is used in gst-libs/gst/gl/Makefile.am so that's the variable
the libraries should be listed in.

I'd say that's an upstream issue - it really looks like it's demanding
X or Wayland to be enabled for OpenGL to work. I'd suggest raising the
issue upsteream.

Thanks,
Paul Barker
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi3] Failed to build gstreamer1.0-plugins-bad with minimal configuration

2016-10-29 Thread Paul Barker
On Fri, 28 Oct 2016 05:56:07 +
Karim ATIKI  wrote:

> Hi Paul,
> 
> 
> Thanks a lot for your feedback and analysis.
> 
> I think it sohuld compile without X11 and Wayland as it's a very
> common configuration
> 
> for RaspberryPi being used with Qt5.x applications.
> 
> 
> Do you think it's bug related to Gstreamer1.0 configuration ?
> 
> 
> 
> Karim
> 

The do_configure log for gstreamer1.0-plugins-bad does contain:

configure: WARNING: X or Wayland is required for OpenGL support

configure.ac in gst-plugins-bad-1.8.3 contains:

dnl EGL
if test "x$HAVE_EGL" = "xno"; then
  if test "x$HAVE_GL" = "xno"; then
AC_MSG_WARN([Building requires either EGL or GLX for OpenGL support])
  fi
else
  if test "x$NEED_EGL" != "xno"; then
if test "x$HAVE_WINDOW_WAYLAND" = "xyes" -o "x$HAVE_WINDOW_X11" = 
"xyes" -o "x$HAVE_WINDOW_DISPMANX" = "xyes"; then
  GL_LIBS="$GL_LIBS -lEGL $EGL_LIBS"
  GL_CFLAGS="$GL_CFLAGS $EGL_CFLAGS"
  USE_EGL=yes
fi
  fi
fi
;;

In config.status EGL_LIBS contains "-lbcm_host -lvcos
-lvchiq_arm", however GL_LIBS only contains "-lGLESv2". So I'd say
EGL_LIBS is not being included in to GL_LIBS because
HAVE_WINDOW_WAYLAND, HAVE_WINDOW_X11 and HAVE_WINDOW_DISPMAX are all
false.

GL_LIBS is used in gst-libs/gst/gl/Makefile.am so that's the variable
the libraries should be listed in.

I'd say that's an upstream issue - it really looks like it's demanding
X or Wayland to be enabled for OpenGL to work. I'd suggest raising the
issue upsteream.

Thanks,
Paul Barker
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi3] Failed to build gstreamer1.0-plugins-bad with minimal configuration

2016-10-27 Thread Karim ATIKI
Hi Paul,


Thanks a lot for your feedback and analysis.

I think it sohuld compile without X11 and Wayland as it's a very common 
configuration

for RaspberryPi being used with Qt5.x applications.


Do you think it's bug related to Gstreamer1.0 configuration ?



Karim




De : Paul Barker 
Envoyé : jeudi 27 octobre 2016 23:18
À : Karim ATIKI
Cc : yocto
Objet : Re: [yocto] [meta-raspberrypi3] Failed to build 
gstreamer1.0-plugins-bad with minimal configuration


gstreamer1.0-plugins-bad compiles if x11, wayland and opengl are all
missing from DISTRO_FEATURES. It fails if x11 and wayland are missing
but opengl is included.

Should it compile if x11 and wayland are removed from DISTRO_FEATURES
but opengl is included? I don't do much on the graphics side so I don't
know if this makes sense as a configuration.

Thanks,
Paul
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi3] Failed to build gstreamer1.0-plugins-bad with minimal configuration

2016-10-27 Thread Khem Raj

> On Oct 27, 2016, at 2:18 PM, Paul Barker  wrote:
> 
> On Thu, 27 Oct 2016 21:26:10 +0100
> Paul Barker  wrote:
> 
>> On Wed, 26 Oct 2016 12:56:11 +
>> Karim ATIKI  wrote:
>> 
>>> Hi all,
>>> 
>>> 
>>> I'm currently unable to build gstreamer1.0-plugins-bad with a clean
>>> checkout of poky-krogoth and also poky-master with
>>> DISTRO_FEATURES_remove = " x11 wayland"
>>> 
>>> 
>>> It fails during the do_compile() task  of gstreamer1.0-plugins-bad
>>> with the following error message:
>>> 
>>> 
>>> undefined reference to graphics_get_display_size().
>>> 
>>> 
>>> This function comes with libbcmhost which is however installed with
>>> userland in sysroot.
>>> 
>>> 
>>> In addition, the log.do_configure of gstreamer1.0-plugins-bad
>>> detects bcm_host as well.
>>> 
>>> 
>>> If I change DISTRO_FEATURES_remove = " x11" it will work.
>>> 
>>> 
>>> I have tested with a minimal configuration & layers:
>>> 
>>> 
>>> Build Configuration:
>>> BB_VERSION= "1.32.0"
>>> BUILD_SYS = "x86_64-linux"
>>> NATIVELSBSTRING   = "Debian-8.2"
>>> TARGET_SYS= "arm-poky-linux-gnueabi"
>>> MACHINE   = "raspberrypi3"
>>> DISTRO= "poky"
>>> DISTRO_VERSION= "2.2"
>>> TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4
>>> callconvention-hard cortexa7" TARGET_FPU= "hard"
>>> meta
>>> meta-poky
>>> meta-yocto-bsp=
>>> "master:ef627ab364d52fe19994c94c1a78fbe21620a32c" meta-raspberrypi
>>> = "master:de016ceef63028f5578191785c50529695f76a1a" meta-oe
>>> meta-multimedia   = "master:8ba31c9ba214802b1305aabbc0be0353cba0bc3e
>>> 
>>> 
>>> and simply launched:
>>> 
>>> 
>>> bitbake -k  gstreamer1.0-plugins-bad
>>> 
>>> 
>> 
>> I've managed to reproduce your issue. Here's the interesting bits of a
>> diff between the do_configure logs, lines removed only exist in the
>> successful build, lines added only exist in the failed build:
>> 
>>@@ -1289,24 +1013,33 @@
>> checking for winsock2.h... no
>> checking for X... no
>> configure: No package 'x11' found
>>+checking for GLES2... yes
>> checking EGL/fbdev_window.h usability... no
>> checking EGL/fbdev_window.h presence... no
>> checking for EGL/fbdev_window.h... no
>>-checking for bcm_host_init in -lbcm_host... no
>>+checking for bcm_host_init in -lbcm_host... yes
>>+checking bcm_host.h usability... yes
>>+checking bcm_host.h presence... yes
>>+checking for bcm_host.h... yes
>>+checking for eglGetProcAddress in -lEGL... yes
>>+checking EGL/egl.h usability... yes
>>+checking EGL/egl.h presence... yes
>>+checking for EGL/egl.h... yes
>>+checking for glEnable in -lGLESv2... yes
>>+checking GLES2/gl2.h usability... yes
>>+checking GLES2/gl2.h presence... yes
>>+checking for GLES2/gl2.h... yes
>> checking for WAYLAND_EGL... no
>> checking libdrm/drm_fourcc.h usability... no
>> checking libdrm/drm_fourcc.h presence... no
>> checking for libdrm/drm_fourcc.h... no
>> checking for GST_ALLOCATORS... yes
>>-host is arm-oe-linux-gnueabi
>>+host is arm-poky-linux-gnueabi
>> configure: WARNING: X or Wayland is required for OpenGL support
>>-configure: WARNING: Either OpenGL or OpenGL|ES is required for
>>OpenGL support -configure: WARNING: Could not find any OpenGL
>>platforms to use such as CGL, WGL or GLX -configure: WARNING:
>> Could not find any window systems to use such as Cocoa, Win32API or
>> X11 -checking for GLeglImageOES... no -checking for GLchar... no
>>-checking for GLsizeiptr... no
>>-checking for GLintptr... no
>>+checking for GLeglImageOES... yes
>>+checking for GLchar... yes
>>+checking for GLsizeiptr... yes
>>+checking for GLintptr... yes
>> checking for GLsync... no
>> checking for GLuint64... no
>> checking for GLint64... no
>>@@ -1610,7 +1343,7 @@
>> 
>> configure: *** checking feature: gl elements ***
>> configure: *** for plug-ins: gl ***
>>-configure: *** These plugins will not be built: gl
>>+configure: *** These plugins will be built: gl
>> 
>> configure: *** checking feature: Gtk+ elements ***
>> configure: *** for plug-ins: gtk ***
>>@@ -2101,6 +1834,7 @@
>>dtls
>>dvb
>>fbdevsink
>>+   gl
>>hls
>>neonhttpsrc
>>rsvg
>>@@ -2131,7 +1865,6 @@
>>faad
>>flite
>>fluidsynth
>>-   gl
>>gme
>>gsmenc gsmdec
>>gtk
>> 
>> ie. In the successful build GLES wasn't detected, which led to the gl
>> plugin not being built, which led to the problem not occurring. That's
>> probably not helpful if you want to be able to use the gl plugin
>> though!
>> 
>> I'm trying to narrow down the differences between these two builds,
>> I'll let you know if I find out any more!
>> 
>> Thanks,
>> Paul
> 
> gstreamer1.0-plugins-bad compiles if x11, wayland and opengl are all
> missing from DISTRO_FEA

Re: [yocto] [meta-raspberrypi3] Failed to build gstreamer1.0-plugins-bad with minimal configuration

2016-10-27 Thread Paul Barker
On Wed, 26 Oct 2016 12:56:11 +
Karim ATIKI  wrote:

> Hi all,
> 
> 
> I'm currently unable to build gstreamer1.0-plugins-bad with a clean
> checkout of poky-krogoth and also poky-master with
> DISTRO_FEATURES_remove = " x11 wayland"
> 
> 
> It fails during the do_compile() task  of gstreamer1.0-plugins-bad
> with the following error message:
> 
> 
> undefined reference to graphics_get_display_size().
> 
> 
> This function comes with libbcmhost which is however installed with
> userland in sysroot.
> 
> 
> In addition, the log.do_configure of gstreamer1.0-plugins-bad detects
> bcm_host as well.
> 
> 
> If I change DISTRO_FEATURES_remove = " x11" it will work.
> 
> 
> I have tested with a minimal configuration & layers:
> 
> 
> Build Configuration:
> BB_VERSION= "1.32.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING   = "Debian-8.2"
> TARGET_SYS= "arm-poky-linux-gnueabi"
> MACHINE   = "raspberrypi3"
> DISTRO= "poky"
> DISTRO_VERSION= "2.2"
> TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4
> callconvention-hard cortexa7" TARGET_FPU= "hard"
> meta
> meta-poky
> meta-yocto-bsp= "master:ef627ab364d52fe19994c94c1a78fbe21620a32c"
> meta-raspberrypi  = "master:de016ceef63028f5578191785c50529695f76a1a"
> meta-oe
> meta-multimedia   = "master:8ba31c9ba214802b1305aabbc0be0353cba0bc3e
> 
> 
> and simply launched:
> 
> 
> bitbake -k  gstreamer1.0-plugins-bad
> 
> 

I've managed to reproduce your issue. Here's the interesting bits of a
diff between the do_configure logs, lines removed only exist in the
successful build, lines added only exist in the failed build:

@@ -1289,24 +1013,33 @@
 checking for winsock2.h... no
 checking for X... no
 configure: No package 'x11' found
+checking for GLES2... yes
 checking EGL/fbdev_window.h usability... no
 checking EGL/fbdev_window.h presence... no
 checking for EGL/fbdev_window.h... no
-checking for bcm_host_init in -lbcm_host... no
+checking for bcm_host_init in -lbcm_host... yes
+checking bcm_host.h usability... yes
+checking bcm_host.h presence... yes
+checking for bcm_host.h... yes
+checking for eglGetProcAddress in -lEGL... yes
+checking EGL/egl.h usability... yes
+checking EGL/egl.h presence... yes
+checking for EGL/egl.h... yes
+checking for glEnable in -lGLESv2... yes
+checking GLES2/gl2.h usability... yes
+checking GLES2/gl2.h presence... yes
+checking for GLES2/gl2.h... yes
 checking for WAYLAND_EGL... no
 checking libdrm/drm_fourcc.h usability... no
 checking libdrm/drm_fourcc.h presence... no
 checking for libdrm/drm_fourcc.h... no
 checking for GST_ALLOCATORS... yes
-host is arm-oe-linux-gnueabi
+host is arm-poky-linux-gnueabi
 configure: WARNING: X or Wayland is required for OpenGL support
-configure: WARNING: Either OpenGL or OpenGL|ES is required for
OpenGL support -configure: WARNING: Could not find any OpenGL
platforms to use such as CGL, WGL or GLX -configure: WARNING: Could
not find any window systems to use such as Cocoa, Win32API or X11
-checking for GLeglImageOES... no -checking for GLchar... no
-checking for GLsizeiptr... no
-checking for GLintptr... no
+checking for GLeglImageOES... yes
+checking for GLchar... yes
+checking for GLsizeiptr... yes
+checking for GLintptr... yes
 checking for GLsync... no
 checking for GLuint64... no
 checking for GLint64... no
@@ -1610,7 +1343,7 @@

 configure: *** checking feature: gl elements ***
 configure: *** for plug-ins: gl ***
-configure: *** These plugins will not be built: gl
+configure: *** These plugins will be built: gl

 configure: *** checking feature: Gtk+ elements ***
 configure: *** for plug-ins: gtk ***
@@ -2101,6 +1834,7 @@
dtls
dvb
fbdevsink
+   gl
hls
neonhttpsrc
rsvg
@@ -2131,7 +1865,6 @@
faad
flite
fluidsynth
-   gl
gme
gsmenc gsmdec
gtk

ie. In the successful build GLES wasn't detected, which led to the gl
plugin not being built, which led to the problem not occurring. That's
probably not helpful if you want to be able to use the gl plugin though!

I'm trying to narrow down the differences between these two builds,
I'll let you know if I find out any more!

Thanks,
Paul
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi3] Failed to build gstreamer1.0-plugins-bad with minimal configuration

2016-10-27 Thread Paul Barker
On Thu, 27 Oct 2016 21:26:10 +0100
Paul Barker  wrote:

> On Wed, 26 Oct 2016 12:56:11 +
> Karim ATIKI  wrote:
> 
> > Hi all,
> > 
> > 
> > I'm currently unable to build gstreamer1.0-plugins-bad with a clean
> > checkout of poky-krogoth and also poky-master with
> > DISTRO_FEATURES_remove = " x11 wayland"
> > 
> > 
> > It fails during the do_compile() task  of gstreamer1.0-plugins-bad
> > with the following error message:
> > 
> > 
> > undefined reference to graphics_get_display_size().
> > 
> > 
> > This function comes with libbcmhost which is however installed with
> > userland in sysroot.
> > 
> > 
> > In addition, the log.do_configure of gstreamer1.0-plugins-bad
> > detects bcm_host as well.
> > 
> > 
> > If I change DISTRO_FEATURES_remove = " x11" it will work.
> > 
> > 
> > I have tested with a minimal configuration & layers:
> > 
> > 
> > Build Configuration:
> > BB_VERSION= "1.32.0"
> > BUILD_SYS = "x86_64-linux"
> > NATIVELSBSTRING   = "Debian-8.2"
> > TARGET_SYS= "arm-poky-linux-gnueabi"
> > MACHINE   = "raspberrypi3"
> > DISTRO= "poky"
> > DISTRO_VERSION= "2.2"
> > TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4
> > callconvention-hard cortexa7" TARGET_FPU= "hard"
> > meta
> > meta-poky
> > meta-yocto-bsp=
> > "master:ef627ab364d52fe19994c94c1a78fbe21620a32c" meta-raspberrypi
> > = "master:de016ceef63028f5578191785c50529695f76a1a" meta-oe
> > meta-multimedia   = "master:8ba31c9ba214802b1305aabbc0be0353cba0bc3e
> > 
> > 
> > and simply launched:
> > 
> > 
> > bitbake -k  gstreamer1.0-plugins-bad
> > 
> > 
> 
> I've managed to reproduce your issue. Here's the interesting bits of a
> diff between the do_configure logs, lines removed only exist in the
> successful build, lines added only exist in the failed build:
> 
> @@ -1289,24 +1013,33 @@
>  checking for winsock2.h... no
>  checking for X... no
>  configure: No package 'x11' found
> +checking for GLES2... yes
>  checking EGL/fbdev_window.h usability... no
>  checking EGL/fbdev_window.h presence... no
>  checking for EGL/fbdev_window.h... no
> -checking for bcm_host_init in -lbcm_host... no
> +checking for bcm_host_init in -lbcm_host... yes
> +checking bcm_host.h usability... yes
> +checking bcm_host.h presence... yes
> +checking for bcm_host.h... yes
> +checking for eglGetProcAddress in -lEGL... yes
> +checking EGL/egl.h usability... yes
> +checking EGL/egl.h presence... yes
> +checking for EGL/egl.h... yes
> +checking for glEnable in -lGLESv2... yes
> +checking GLES2/gl2.h usability... yes
> +checking GLES2/gl2.h presence... yes
> +checking for GLES2/gl2.h... yes
>  checking for WAYLAND_EGL... no
>  checking libdrm/drm_fourcc.h usability... no
>  checking libdrm/drm_fourcc.h presence... no
>  checking for libdrm/drm_fourcc.h... no
>  checking for GST_ALLOCATORS... yes
> -host is arm-oe-linux-gnueabi
> +host is arm-poky-linux-gnueabi
>  configure: WARNING: X or Wayland is required for OpenGL support
> -configure: WARNING: Either OpenGL or OpenGL|ES is required for
> OpenGL support -configure: WARNING: Could not find any OpenGL
> platforms to use such as CGL, WGL or GLX -configure: WARNING:
> Could not find any window systems to use such as Cocoa, Win32API or
> X11 -checking for GLeglImageOES... no -checking for GLchar... no
> -checking for GLsizeiptr... no
> -checking for GLintptr... no
> +checking for GLeglImageOES... yes
> +checking for GLchar... yes
> +checking for GLsizeiptr... yes
> +checking for GLintptr... yes
>  checking for GLsync... no
>  checking for GLuint64... no
>  checking for GLint64... no
> @@ -1610,7 +1343,7 @@
> 
>  configure: *** checking feature: gl elements ***
>  configure: *** for plug-ins: gl ***
> -configure: *** These plugins will not be built: gl
> +configure: *** These plugins will be built: gl
> 
>  configure: *** checking feature: Gtk+ elements ***
>  configure: *** for plug-ins: gtk ***
> @@ -2101,6 +1834,7 @@
> dtls
> dvb
> fbdevsink
> +   gl
> hls
> neonhttpsrc
> rsvg
> @@ -2131,7 +1865,6 @@
> faad
> flite
> fluidsynth
> -   gl
> gme
> gsmenc gsmdec
> gtk
> 
> ie. In the successful build GLES wasn't detected, which led to the gl
> plugin not being built, which led to the problem not occurring. That's
> probably not helpful if you want to be able to use the gl plugin
> though!
> 
> I'm trying to narrow down the differences between these two builds,
> I'll let you know if I find out any more!
> 
> Thanks,
> Paul

gstreamer1.0-plugins-bad compiles if x11, wayland and opengl are all
missing from DISTRO_FEATURES. It fails if x11 and wayland are missing
but opengl is included.

Should it compile 

[yocto] [meta-raspberrypi3] Failed to build gstreamer1.0-plugins-bad with minimal configuration

2016-10-26 Thread Karim ATIKI
Hi all,


I'm currently unable to build gstreamer1.0-plugins-bad with a clean checkout of 
poky-krogoth and also poky-master with DISTRO_FEATURES_remove = " x11 wayland"


It fails during the do_compile() task  of gstreamer1.0-plugins-bad  with the 
following error message:


undefined reference to graphics_get_display_size().


This function comes with libbcmhost which is however installed with userland in 
sysroot.


In addition, the log.do_configure of gstreamer1.0-plugins-bad detects bcm_host 
as well.


If I change DISTRO_FEATURES_remove = " x11" it will work.


I have tested with a minimal configuration & layers:


Build Configuration:
BB_VERSION= "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Debian-8.2"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "raspberrypi3"
DISTRO= "poky"
DISTRO_VERSION= "2.2"
TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard 
cortexa7"
TARGET_FPU= "hard"
meta
meta-poky
meta-yocto-bsp= "master:ef627ab364d52fe19994c94c1a78fbe21620a32c"
meta-raspberrypi  = "master:de016ceef63028f5578191785c50529695f76a1a"
meta-oe
meta-multimedia   = "master:8ba31c9ba214802b1305aabbc0be0353cba0bc3e


and simply launched:


bitbake -k  gstreamer1.0-plugins-bad


Has anyone already experienced this issue with raspberrypi3 ?



Cheers,


Karim


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto