| Summary: | Cross compiling patches | ||||||
|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Joerg Sonnenberger <joerg> | ||||
| Component: | Lib/Xlib | Assignee: | Xorg Project Team <xorg-team> | ||||
| Status: | RESOLVED DUPLICATE | QA Contact: | Xorg Project Team <xorg-team> | ||||
| Severity: | enhancement | ||||||
| Priority: | medium | CC: | mat | ||||
| Version: | git | Keywords: | patch | ||||
| Hardware: | All | ||||||
| OS: | NetBSD | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
|
Description
Joerg Sonnenberger
2007-11-30 08:41:56 UTC
Created attachment 12871 [details] [review] Allow cross-compiling of libX11 *** This bug has been marked as a duplicate of bug 6669 *** On Tue, Feb 17, 2009 at 06:16:23AM -0800, bugzilla-daemon@freedesktop.org wrote: > *** This bug has been marked as a duplicate of bug 6669 *** Did you even compare the patches? The patch in this PR can actually be applied, the one in 6669 is just a hack. Joerg > --- Comment #3 from Joerg Sonnenberger <joerg@NetBSD.org> 2009-02-17 07:45:22 PST --- > Did you even compare the patches? The patch in this PR can actually be > applied, the one in 6669 is just a hack. no, i didn't compare the patches, because another one has been applied anyway. commit 58bf3aa746908f01c37be7045699e43a4e270944 Author: John Tapsell <johnflux@gmail.com> Date: Tue Sep 23 17:30:13 2008 +0300 Build: Use native compiler for makekeys makekeys needs to be run during the build process, as opposed to on the target, so build it with either of gcc or cc to fix cross-compiling. This can be overridden by setting $CC_FOR_BUILD. and amended in: commit 0877bc916afbd1ff8f1833edc930b765ea783576 Author: Daniel Stone <daniel@fooishbar.org> Date: Tue Sep 23 19:02:02 2008 +0300 configure.ac: Fix CC_FOR_BUILD logic error Turns out we were accidentally smashing it so that you couldn't set it externally at all. Oops. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.