From: Ulrich Hecht <uli@suse.de>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] directfb URL
Date: Thu, 14 Dec 2006 17:22:16 +0100 [thread overview]
Message-ID: <200612141722.16866.uli@suse.de> (raw)
In-Reply-To: <20061214153540.GA2094@aon.at>
Hi!
On Thursday 14 December 2006 16:35, Bernhard Fischer wrote:
> On Thu, Dec 14, 2006 at 04:23:28PM +0100, Ulrich Hecht wrote:
> >0.9.25.1 has been moved to Old.
>
> And anyone who touches this, please also check that it gets passed the
> proper flags (the staging-dir libs, not the host ones..)
> http://bugs.busybox.net/view.php?id?9
This patch makes directfb build and fixes #959 and similar issues.
- fixes prefix for libsysfs and libpng so that correct .la files are
being generated
- same for directfb, plus moves it from $(STAGING_DIR)/usr to
$(STAGING_DIR)
- fixes PAGE_SIZE issue in directfb
CU
Uli
-------------- next part --------------
A non-text attachment was scrubbed...
Name: directfb.patch
Type: text/x-diff
Size: 4146 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20061214/57c7c124/attachment.bin
prev parent reply other threads:[~2006-12-14 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 15:23 [Buildroot] [patch] directfb URL Ulrich Hecht
2006-12-14 15:35 ` Bernhard Fischer
2006-12-14 16:22 ` Ulrich Hecht [this message]
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=200612141722.16866.uli@suse.de \
--to=uli@suse.de \
--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