From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 323] New: gen_matypes fails to execute during build of Mesa when using cross toolchain
Date: Fri, 8 May 2009 08:01:36 +0000 (UTC) [thread overview]
Message-ID: <bug-323-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=323
Host: x86 and x86_64
Target: i686
Summary: gen_matypes fails to execute during build of Mesa when
using cross toolchain
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: spambox at nurd.se
CC: buildroot at uclibc.org
Estimated Hours: 0.1
Created an attachment (id=291)
--> (https://bugs.busybox.net/attachment.cgi?id=291)
patch to build gen_matypes using the host compiler
gen_matypes is built with the cross toolchain. In my case i was using the
uClibc toolchain and gen_matypes is built depending on uClibc.
gen_matypes is executed on the build host during the build in order to generate
an .h-file. This execution fails if the build host does not have uClibc.
A simple solution is to build gen_matypes using the host compiler.
I have attached a proposed patch that fixes the problem:
package/x11r7/mesa3d/mesa3d-7.2-gen_matypes-fix.patch
Patch have been tested successfully on x86 and x86_64 build hosts using i686 as
a target architecture.
--
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-05-08 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 8:01 bugzilla at busybox.net [this message]
2009-05-08 8:02 ` [Buildroot] [Bug 323] gen_matypes fails to execute during build of Mesa when using cross toolchain bugzilla at busybox.net
2009-05-19 15:35 ` 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-323-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.