All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Otavio Salvador" <otavio.salvador@ossystems.com.br>
To: Georg Hartinger <Georg.Hartinger@congatec.com>
Cc: "meta-freescale@lists.yoctoproject.org"
	<meta-freescale@lists.yoctoproject.org>
Subject: Re: [meta-freescale] gstreamer-plugins-bad build error in dunfell for SABRESD platform
Date: Mon, 28 Sep 2020 14:26:44 -0300	[thread overview]
Message-ID: <CAP9ODKqNraBYadUGYqnXcf0NAVQs03n2Pz4F8Cee74=dOeivcA@mail.gmail.com> (raw)
In-Reply-To: <AM0PR0402MB35697DD7E6515F35D0E9A40B8D350@AM0PR0402MB3569.eurprd04.prod.outlook.com>

Hello Georg,

Em seg., 28 de set. de 2020 às 13:18, Georg Hartinger
<Georg.Hartinger@congatec.com> escreveu:
>
> I get build errors when building plain yocto Dunfell for the iMX6 SABRESD plattform (not mainline)
>
> The setup was (under Ubuntu 16.04):
> $ repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dunfell
> $ MACHINE=imx6qdlsabresd DISTRO=fsl-wayland source setup-environment build-fsl-wayland
> $ bitbake fsl-image-machine-test
>
>
> The error is in gstreamer1.0-plugins-bad_1.16.imx:
>
> a2e124a@@gstwaylandsink@sha/wlvideoformat.c.o' -c ../git/ext/wayland/wlvideoformat.c
> | In file included from ../git/ext/wayland/wlvideoformat.c:30:
> | ../git/ext/wayland/wlvideoformat.h:29:10: fatal error: drm_fourcc.h: No such file or directory
> | 29 | #include <drm_fourcc.h>
>
> The correct include path for this file would be <libdrm/drm_fourcc.h> so if I change all those includes it works.
> But also all "#include <drm.h>" inside the recipe-sysroot folder have to be replaced with "#include <libdrm/drm.h>".
>
> The strange thing is, that the gstreamer1.0-plugins-base does have that extended include path (also in the recipe-sysroot folder)
>
> Any idea on how to fix this? I know I could write a patch for the sources itself, but how to handle the recipe-sysroot folder stuff?


Please check the meta-freescale at dunfell-next branch and see if you
reproduce the issue.


-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750

  reply	other threads:[~2020-09-28 17:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28 16:17 gstreamer-plugins-bad build error in dunfell for SABRESD platform Georg Hartinger
2020-09-28 17:26 ` Otavio Salvador [this message]
2020-09-28 21:24 [meta-freescale] " Georg Hartinger
2020-09-29  9:56 Georg Hartinger
2020-09-29 11:36 ` Otavio Salvador
2020-09-29 16:29   ` Georg Hartinger
2020-09-29 16:43     ` Otavio Salvador
2020-09-29 19:24       ` Georg Hartinger
2020-09-29 19:31         ` Otavio Salvador
2020-09-30  8:18           ` Georg Hartinger
2020-09-30 11:44             ` Otavio Salvador
2020-09-30 17:51               ` Georg Hartinger
2020-09-30 18:18                 ` Otavio Salvador
2020-10-02 13:14                   ` Georg Hartinger
2020-10-02 13:23                     ` [meta-freescale] " Otavio Salvador
2020-10-05  7:51                       ` Georg Hartinger
2020-10-05 12:17                         ` [meta-freescale] " Otavio Salvador
2020-09-29 17:06     ` Andrey Zhizhikin
2020-09-29 19:14       ` Georg Hartinger
2020-09-30  6:32         ` Andrey Zhizhikin

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='CAP9ODKqNraBYadUGYqnXcf0NAVQs03n2Pz4F8Cee74=dOeivcA@mail.gmail.com' \
    --to=otavio.salvador@ossystems.com.br \
    --cc=Georg.Hartinger@congatec.com \
    --cc=meta-freescale@lists.yoctoproject.org \
    /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.