From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2983] New: xlib_libX11 build failed
Date: Fri, 17 Dec 2010 09:42:16 +0000 (UTC) [thread overview]
Message-ID: <bug-2983-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=2983
Summary: xlib_libX11 build failed
Product: buildroot
Version: 2010.05
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: miroslav.ignjatovic at rt-rk.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Build stops for cross-building on libX11. release 2010.11
A minor bug (maybe copy-paste error).
file(buildroot-2010.11/package/x11r7/xlib_libX11/xlib_libX11.mk)
-- before -----------------------------------------------------------
define XLIB_LIBX11_BUILD_MAKEKEYS_FOR_HOST
cd $(@D)/src/util && $(HOSTCC) $(HOSTCFLAGS) \
-I$(STAGING_DIR)/usr/include -o makekeys makekeys.c
endef
-- after ------------------------------------------------------------
define XLIB_LIBX11_BUILD_MAKEKEYS_FOR_HOST
cd $(@D)/src/util && $(HOSTCC) $(HOSTCFLAGS) \
-o makekeys makekeys.c
endef
---------------------------------------------------------------------
-I$(STAGING_DIR)/usr/include should be replaced with "maybe" something else.
In our case just removing it, solved the problem.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2010-12-17 9:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 9:42 bugzilla at busybox.net [this message]
2010-12-17 9:44 ` [Buildroot] [Bug 2983] xlib_libX11 build failed bugzilla at busybox.net
2010-12-21 11:01 ` bugzilla at busybox.net
2010-12-21 13:52 ` bugzilla at busybox.net
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=bug-2983-163@https.bugs.busybox.net/ \
--to=bugzilla@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.