Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Henrik Frilund <henrik.frilund@convergens.fi>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot, none working GStreamer
Date: Thu, 28 Feb 2013 17:31:19 +0200	[thread overview]
Message-ID: <512F7847.7090107@convergens.fi> (raw)
In-Reply-To: <mailman.101702.1362062313.32592.buildroot@busybox.net>

Hello,
  I have question regarding the build of GStreamer in buildroot 2012-08 
and 2012-11-01.
I have a custom board that is based around a Texas am335x chip which is 
a ARM Cortex A8 chip.
The embedded application I have is built around GStreamer and I use 
buildroot to build the rootfs
and the app itself.
  The problem i have encountered is that if I use any newer compiler 
than Sourcery 2010q1 of the external tool chains I get a broken 
GStreamer build. This meaning that the built gstreamer fails with
SIGABRT as soon as I launch the application.
  The same behaviour can be seen if i just do gst-inspect on the console 
with a debug level >3.

The things that I've noticed that on the broken builds in the debug 
information the thread ID information
is missing so what could cause that to happen.

I've talked to some of the GStreamer developers and they thought is was 
a toolchain issue but I'm having
a hard time believing that all newer sourcery toolchains and Linaro ones 
have the same issue. I also tried to build a custom toolchain with 
crosstool-ng but it has the same issue.

Anyone encountered anything like this before?

BR

//H

           reply	other threads:[~2013-02-28 15:31 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <mailman.101702.1362062313.32592.buildroot@busybox.net>]

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=512F7847.7090107@convergens.fi \
    --to=henrik.frilund@convergens.fi \
    --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