From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 3/4] freetype: enable 64 bit file support
Date: Thu, 5 Jun 2014 17:09:04 -0700 [thread overview]
Message-ID: <1402013345-24930-4-git-send-email-sgw@linux.intel.com> (raw)
In-Reply-To: <1402013345-24930-1-git-send-email-sgw@linux.intel.com>
When running 32bit code on a large filessytem with 64bit inodes, the
fontcache was not being created correctly because an EOVERFLOW was being
returned from the fstat when reading the 64 inode on a 32bit system.
The fontcache is created at rootfs time on the host system via qemu.
[YOCTO #6338]
Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
meta/recipes-graphics/freetype/freetype_2.5.3.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-graphics/freetype/freetype_2.5.3.bb b/meta/recipes-graphics/freetype/freetype_2.5.3.bb
index 0944d83..2c861de 100644
--- a/meta/recipes-graphics/freetype/freetype_2.5.3.bb
+++ b/meta/recipes-graphics/freetype/freetype_2.5.3.bb
@@ -25,6 +25,8 @@ LIBTOOL = "${S}/builds/unix/${HOST_SYS}-libtool"
EXTRA_OEMAKE = "'LIBTOOL=${LIBTOOL}'"
EXTRA_OEMAKE_class-native = ""
EXTRA_OECONF = "--without-zlib --without-bzip2 CC_BUILD='${BUILD_CC}'"
+TARGET_CPPFLAGS += "-D_FILE_OFFSET_BITS=64"
+
PACKAGECONFIG ??= ""
PACKAGECONFIG[pixmap] = "--with-png,--without-png,libpng"
--
1.8.3.1
next prev parent reply other threads:[~2014-06-06 0:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 0:09 [PATCH 0/4] 4 Bug fixes! Saul Wold
2014-06-06 0:09 ` [PATCH 1/4] update-rc.d/useradd: Add additional dependecies Saul Wold
2014-06-10 11:57 ` Phil Blundell
2014-06-10 14:38 ` Saul Wold
2014-06-10 14:53 ` Phil Blundell
2014-06-16 14:47 ` Paul Eggleton
2014-06-17 13:18 ` Phil Blundell
2014-06-17 17:01 ` Paul Eggleton
2014-06-06 0:09 ` [PATCH 2/4] busybox: put udhcpc in background Saul Wold
2014-06-06 0:09 ` Saul Wold [this message]
2014-06-06 0:09 ` [PATCH 4/4] fontconfig: enable 64 bit file support Saul Wold
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=1402013345-24930-4-git-send-email-sgw@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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