From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 559] New: mesa3d build fails
Date: Tue, 11 Aug 2009 12:34:24 +0000 (UTC) [thread overview]
Message-ID: <bug-559-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=559
Host: i686
Target: i686
Build: x86_64
Summary: mesa3d build fails
Product: buildroot
Version: unspecified
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: fpasch at googlemail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Hello!
Just tried to compile x11 for x86 on a x86_64 machine with
buildroot-2009.08-rc2. I'm using an external glibc-toolchain (created by
crosstool-ng)
Build of Mesa 7.2 fails with:
/home/test/crosstool-ng/i686-unknown-linux-gnu/lib/gcc/i686-unknown-linux-gnu/4.3.2/../../../../i686-unknown-linux-gnu/bin/ld:
cannot find -lX11
collect2: ld returned 1 exit status
My current workaround is:
--- 1/package/x11r7/mesa3d/mesa3d.mk~ 2009-08-11 14:30:37.000000000 +0200
+++ 2/package/x11r7/mesa3d/mesa3d.mk 2009-08-11 14:30:42.000000000 +0200
@@ -47,7 +47,7 @@
echo "SRC_DIRS = glx/x11 mesa glu glut/glx" && \
echo "USING_EGL = 0" && \
echo "X11_INCLUDES = " && \
- echo "EXTRA_LIB_PATH = " && \
+ echo "EXTRA_LIB_PATH = -L$(STAGING_DIR)/usr/lib" && \
echo "PROGRAM_DIRS =" && \
echo "MKDEP_OPTIONS = -fdepend -Y$(STAGING_DIR)/usr/include
-I$(MESA_GCCINCLUDE)" \
) >> $(MESA_CONFIG_FILE)
--
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:[~2009-08-11 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 12:34 bugzilla at busybox.net [this message]
2009-08-26 20:50 ` [Buildroot] [Bug 559] mesa3d build fails bugzilla at busybox.net
2009-08-27 8:34 ` bugzilla at busybox.net
2009-12-01 13:50 ` bugzilla at busybox.net
2009-12-01 13:54 ` bugzilla at busybox.net
2009-12-06 19:14 ` 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-559-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.