From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0003834]: cairo build broken when directfb support is required
Date: Fri, 20 Jun 2008 19:19:55 -0700 [thread overview]
Message-ID: <bb1ae9751e255807f2b801d4f8fa6ab3@busybox.net> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=3834
======================================================================
Reported By: kjzhang
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 3834
Category: Architecture Specific
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
======================================================================
Date Submitted: 06-20-2008 19:19 PDT
Last Modified: 06-20-2008 19:19 PDT
======================================================================
Summary: cairo build broken when directfb support is required
Description:
After applying the patch uploaded in 0003584(adding directfb dependency),
cairo doens't build because of missing "directfb.h" when compiling
cairo-directfb-surface.c.
I'm trying to build libgtk2 on top of directfb instead of X for both i686
and arrm, the above problem happens in both cases.
Does anybody else see the same issue?
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
06-20-08 19:19 kjzhang New Issue
06-20-08 19:19 kjzhang Status new => assigned
06-20-08 19:19 kjzhang Assigned To => buildroot
======================================================================
next reply other threads:[~2008-06-21 2:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 2:19 bugs at busybox.net [this message]
2008-06-23 12:13 ` [Buildroot] [buildroot 0003834]: cairo build broken when directfb support is required Daniel Laird
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=bb1ae9751e255807f2b801d4f8fa6ab3@busybox.net \
--to=bugs@busybox.net \
--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