From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0000754]: "prefix" path is used to retrieve data files by directfb
Date: Mon, 12 Feb 2007 05:46:18 -0800 [thread overview]
Message-ID: <faf6a675cbdeb40eb80944cabe7529ec@bugs.busybox.net> (raw)
The following issue has been ASSIGNED.
======================================================================
http://busybox.net/bugs/view.php?id=754
======================================================================
Reported By: vspaceg
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 754
Category: Architecture Specific
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 02-23-2006 09:43 PST
Last Modified: 02-12-2007 05:46 PST
======================================================================
Summary: "prefix" path is used to retrieve data files by
directfb
Description:
Directfb is using the "prefix" path to retrieve data files.
So the host path of the build appears as missing when I execute on the
target.
Work-around:
I patched directfb this way, in order to have "prefix" having two
different values when compiling and when installing:
(note: look for "--prefix="):
$(DIRECTFB_DIR)/.configured: $(DIRECTFB_DIR)/.unpacked
(cd $(DIRECTFB_DIR); \
$(TARGET_CONFIGURE_OPTS) \
CFLAGS="$(TARGET_CFLAGS) -I$(STAGING_DIR)/usr/include" \
LDFLAGS="-L$(STAGING_DIR)/lib -L$(STAGING_DIR)/usr/lib" \
ac_cv_header_linux_wm97xx_h=no \
ac_cv_header_linux_sisfb_h=no \
./configure \
--target=$(GNU_TARGET_NAME) \
--host=$(GNU_TARGET_NAME) \
--build=$(GNU_HOST_NAME) \
--prefix=/usr \
--with-gfxdrivers=cle266,unichrome \
--enable-jpeg \
[...]
(note: look for "prefix=")
$(STAGING_DIR)/usr/lib/libdirectfb.so: $(DIRECTFB_DIR)/.compiled
$(MAKE) -C $(DIRECTFB_DIR) install prefix=$(STAGING_DIR)/usr
$(MAKE) -C $(DIRECTFB_DIR)/lib/fusion install prefix=$(STAGING_DIR)/usr
$(MAKE) -C $(DIRECTFB_DIR)/lib/direct install prefix=$(STAGING_DIR)/usr
touch -c $(STAGING_DIR)/lib/libdirectfb.so
======================================================================
----------------------------------------------------------------------
andersen - 04-06-06 10:49
----------------------------------------------------------------------
This problem is now fixed
Issue History
Date Modified Username Field Change
======================================================================
02-23-06 09:43 vspaceg New Issue
02-23-06 09:43 vspaceg Status new => assigned
02-23-06 09:43 vspaceg Assigned To => uClibc
04-06-06 10:49 andersen Note Added: 0001230
04-06-06 10:49 andersen Status assigned => closed
04-06-06 10:49 andersen Resolution open => fixed
02-12-07 05:46 vapier Status closed => assigned
02-12-07 05:46 vapier Assigned To uClibc => buildroot
======================================================================
reply other threads:[~2007-02-12 13:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=faf6a675cbdeb40eb80944cabe7529ec@bugs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.