Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] DirectFB backend of Gtk?
Date: Tue, 27 Mar 2012 11:38:52 +0200	[thread overview]
Message-ID: <20120327113852.6801b8f3@skate> (raw)
In-Reply-To: <1332838194-3638-2-git-send-email-yegorslists@googlemail.com>

Hello,

Le Tue, 27 Mar 2012 10:49:54 +0200,
yegorslists at googlemail.com a ?crit :

> diff --git a/package/directfb/directfb.mk b/package/directfb/directfb.mk
> index 977d272..071cdf4 100644
> --- a/package/directfb/directfb.mk
> +++ b/package/directfb/directfb.mk
> @@ -4,7 +4,7 @@
>  #
>  #############################################################
>  DIRECTFB_VERSION_MAJOR = 1.4
> -DIRECTFB_VERSION = $(DIRECTFB_VERSION_MAJOR).15
> +DIRECTFB_VERSION = $(DIRECTFB_VERSION_MAJOR).16
>  DIRECTFB_SITE = http://www.directfb.org/downloads/Core/DirectFB-$(DIRECTFB_VERSION_MAJOR)
>  DIRECTFB_SOURCE = DirectFB-$(DIRECTFB_VERSION).tar.gz
>  DIRECTFB_AUTORECONF = YES

By any chance, are you using the DirectFB backend of Gtk? We have some
build failures with it:
http://autobuild.buildroot.org/results/e6e611073582ae59ef9a7cb66415b998e6b815f4/.

If someone could have a look at this, it would be nice.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-03-27  9:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27  8:49 [Buildroot] [PATCH 1/2] feh: bump to 2.5 yegorslists at googlemail.com
2012-03-27  8:49 ` [Buildroot] [PATCH 2/2] directfb: bump to 1.4.16 yegorslists at googlemail.com
2012-03-27  9:38   ` Thomas Petazzoni [this message]
2012-04-04 20:22   ` Peter Korsgaard
2012-04-04 20:10 ` [Buildroot] [PATCH 1/2] feh: bump to 2.5 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=20120327113852.6801b8f3@skate \
    --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