From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] directfb: bump to version 1.4.13
Date: Thu, 11 Aug 2011 19:34:37 +0200 [thread overview]
Message-ID: <1313084078.12036.12.camel@bender> (raw)
In-Reply-To: <C2A5D1386C6DB94198F2A5C8368EAE6C143B59F0@DULMEX02.barco.com>
On Thu, 2011-08-11 at 12:51 -0400, Fei, Yiyang wrote:
> The newest release of directfb is actually 1.5.3. Is there a specific
> reason you need to stick with 1.4.x? V1.5.3 also has build issues due
> to ARM v6 instructions which are not supported on my processor. I'm
> working with directfb to resolve it.
I understood that 1.4.x is still the latest stable branch and that 1.5.x
is an unstable development branch. And as far as I know 1.4.13 is the
latest version that will cross-compile w/o problems.
Sven
next prev parent reply other threads:[~2011-08-11 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.15.1313064002.17111.buildroot@busybox.net>
2011-08-11 16:51 ` [Buildroot] [PATCH] directfb: bump to version 1.4.13 Fei, Yiyang
2011-08-11 17:34 ` Sven Neumann [this message]
2011-08-11 10:44 Sven Neumann
2011-08-12 19:35 ` Peter Korsgaard
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=1313084078.12036.12.camel@bender \
--to=s.neumann@raumfeld.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