From: spdawson at gmail.com <spdawson@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lcdproc: fix autobuild errors
Date: Sun, 25 Nov 2012 15:52:43 +0000 [thread overview]
Message-ID: <1353858764-28962-1-git-send-email-spdawson@gmail.com> (raw)
From: Simon Dawson <spdawson@gmail.com>
The autobuilders are falling over building lcdproc, with failures like the
following.
http://autobuild.buildroot.net/results/622b7da10be751c725ba25eb40102269790b4b03/build-end.log
As Thomas Petazzoni has pointed out, the compile command lines incorrectly
contain host header and library search paths, such as the following.
-I/home/peko/scratch/host/usr/include/freetype2
-L/home/peko/scratch/host/usr/lib -lfreetype
This patch changes the lcdproc package to pass the freetype installation
prefixes on the configure command line.
Signed-off-by: Simon Dawson <spdawson@gmail.com>
---
package/lcdproc/lcdproc.mk | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/package/lcdproc/lcdproc.mk b/package/lcdproc/lcdproc.mk
index 2a80289..fe88f46 100644
--- a/package/lcdproc/lcdproc.mk
+++ b/package/lcdproc/lcdproc.mk
@@ -10,7 +10,9 @@ LCDPROC_LICENSE = GPLv2+
LCDPROC_LICENSE_FILES = COPYING
LCDPROC_MAKE = $(MAKE1)
-LCDPROC_CONF_OPT = --enable-drivers=$(BR2_PACKAGE_LCDPROC_DRIVERS)
+LCDPROC_CONF_OPT = --enable-drivers=$(BR2_PACKAGE_LCDPROC_DRIVERS) \
+ --with-ft-prefix="$(STAGING_DIR)/usr" \
+ --with-ft-exec-prefix="$(STAGING_DIR)/usr"
ifeq ($(BR2_PACKAGE_LCDPROC_MENUS),y)
LCDPROC_CONF_OPT += --enable-lcdproc-menus
--
1.7.10.4
next reply other threads:[~2012-11-25 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 15:52 spdawson at gmail.com [this message]
2012-11-26 18:17 ` [Buildroot] [PATCH] lcdproc: fix autobuild errors 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=1353858764-28962-1-git-send-email-spdawson@gmail.com \
--to=spdawson@gmail.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