From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] gst-plugins-ugly fail to build
Date: Mon, 3 May 2010 12:20:30 +0200 [thread overview]
Message-ID: <20100503122030.307ec66f@surf> (raw)
In-Reply-To: <4BDEA010.4010509@digi.com>
On Mon, 3 May 2010 12:06:08 +0200
Javier Viguera <javier.viguera@digi.com> wrote:
> My current setup is latest buildroot (git sha1 0cd0d0647) with external
> toolchain built with crosstool-NG (arm + eglibc toolchain).
I'm not sure where 0cd0d0647 is, but can you try after applying
http://git.potipota.net/cgi-bin/cgit.cgi/buildroot/patch/?id=566f764523ac2de8dfd87742f63099896c4bb5f6 ?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-05-03 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 10:06 [Buildroot] gst-plugins-ugly fail to build Javier Viguera
2010-05-03 10:20 ` Thomas Petazzoni [this message]
2010-05-03 10:22 ` Lionel Landwerlin
2010-05-03 12:23 ` Javier Viguera
2010-05-03 12:41 ` Thomas Petazzoni
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=20100503122030.307ec66f@surf \
--to=thomas.petazzoni@free-electrons.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