From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Fix building ghostcript variants on Ubuntu 11.10
Date: Tue, 27 Sep 2011 14:12:53 -0700 [thread overview]
Message-ID: <cover.1317157793.git.josh@linux.intel.com> (raw)
Ubuntu 11.10 has moved sys/time.h such that the hard-coded test paths in
ghostscripts configuration scripts fails.
This patch works around that issue.
Regards,
Joshua
The following changes since commit 684a4b517d13884c315688967fadd5e6a4845b71:
libffi: really populate -dev package (2011-09-26 20:50:27 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib josh/work
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=josh/work
Joshua Lock (1):
ghostscript: disable check for time.h
.../ghostscript/ghostscript_9.02.bb | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
--
1.7.6.2
next reply other threads:[~2011-09-27 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 21:12 Joshua Lock [this message]
2011-09-27 21:12 ` [PATCH 1/1] ghostscript: disable check for time.h Joshua Lock
2011-09-27 21:20 ` Joshua Lock
2011-09-28 16:17 ` [PATCH 0/1] Fix building ghostcript variants on Ubuntu 11.10 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=cover.1317157793.git.josh@linux.intel.com \
--to=josh@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