Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Help about gstreamer h264 in buildroot
Date: Sat, 21 Jun 2014 13:04:14 +0200	[thread overview]
Message-ID: <53A566AE.7020800@gmail.com> (raw)
In-Reply-To: <20140614141451.6780163c@free-electrons.com>

Il 14/06/2014 14:14, Thomas Petazzoni ha scritto:
> I tried building your configuration, and here it fails with a different
> issue:
>
> .obj/qeglfshooks_pi.o: In function `QEglFSPiHooks::destroyNativeWindow(void*)':
> qeglfshooks_pi.cpp:(.text+0x2c): undefined reference to `vc_dispmanx_update_start'
> qeglfshooks_pi.cpp:(.text+0x38): undefined reference to `vc_dispmanx_element_remove'
> qeglfshooks_pi.cpp:(.text+0x40): undefined reference to `vc_dispmanx_update_submit_sync'
> .obj/qeglfshooks_pi.o: In function `QEglFSPiHooks::platformDestroy()':
> qeglfshooks_pi.cpp:(.text+0x90): undefined reference to `vc_dispmanx_display_close'
> .obj/qeglfshooks_pi.o: In function `QEglFSPiHooks::platformDisplay() const':
> qeglfshooks_pi.cpp:(.text+0xa0): undefined reference to `vc_dispmanx_display_open'
> .obj/qeglfshooks_pi.o: In function `QEglFSPiHooks::createNativeWindow(QPlatformWindow*, QSize const&, QSurfaceFormat const&)':
> qeglfshooks_pi.cpp:(.text+0x10c): undefined reference to `vc_dispmanx_update_start'
> qeglfshooks_pi.cpp:(.text+0x15c): undefined reference to `vc_dispmanx_element_add'
> qeglfshooks_pi.cpp:(.text+0x168): undefined reference to `vc_dispmanx_update_submit_sync'
> collect2: error: ld returned 1 exit status
>
> That's an issue with the RPi OpenGL implementation, I think we have had
> a couple of similar failures in the autobuilders. Maxime, Yann, any
> suggestion?



Hi Thomas, after fixing the gst-ffmpeg issue thanks to Arnout 
Vandecappelle, I'm still trying to compile buildroot and now I'm facing 
the problem you reported above.

Do you confirm this doesn't work?

I'm very confused how to skip around all those bugs in order to have a 
functional buildroot environment.

Marco

  parent reply	other threads:[~2014-06-21 11:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-14  9:19 [Buildroot] Help about gstreamer h264 in buildroot Marco Trapanese
2014-06-14 12:14 ` Thomas Petazzoni
2014-06-14 19:50   ` Marco Trapanese
2014-06-14 22:34     ` Thomas Petazzoni
2014-06-17 12:54       ` Marco Trapanese
2014-06-17 13:18         ` Thomas Petazzoni
2014-06-21 11:04   ` Marco Trapanese [this message]
2014-06-21 13:04     ` Thomas Petazzoni
2014-06-21 13:23       ` Marco Trapanese
2014-06-21 16:23         ` Marco Trapanese
2014-06-18 23:13 ` Arnout Vandecappelle

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=53A566AE.7020800@gmail.com \
    --to=marcotrapanese@gmail.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox