Bug 23590 - xf86-video-geode 2.11.4 does not compile on AMD64
Summary: xf86-video-geode 2.11.4 does not compile on AMD64
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/geode (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) NetBSD
: medium blocker
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-29 08:48 UTC by Thomas Klausner
Modified: 2009-09-01 05:05 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Thomas Klausner 2009-08-29 08:48:27 UTC
--- lx_driver.lo ---
/var/tmp//cc9jbDio.s: Assembler messages:
/var/tmp//cc9jbDio.s:1097: Error: suffix or operands invalid for `push'
/var/tmp//cc9jbDio.s:1102: Error: suffix or operands invalid for `mov'
/var/tmp//cc9jbDio.s:1103: Error: suffix or operands invalid for `mov'
/var/tmp//cc9jbDio.s:1104: Error: suffix or operands invalid for `mov'
/var/tmp//cc9jbDio.s:1108: Error: suffix or operands invalid for `pop'

--- durango.lo ---
/var/tmp//cc9nhG2D.s: Assembler messages:
/var/tmp//cc9nhG2D.s:9132: Error: suffix or operands invalid for `push'
/var/tmp//cc9nhG2D.s:9137: Error: suffix or operands invalid for `mov'
/var/tmp//cc9nhG2D.s:9138: Error: suffix or operands invalid for `mov'
/var/tmp//cc9nhG2D.s:9139: Error: suffix or operands invalid for `mov'
/var/tmp//cc9nhG2D.s:9143: Error: suffix or operands invalid for `pop'

That's on NetBSD-5.99.15/amd64 with gcc (GCC) 4.1.3 20080704 prerelease (NetBSD nb2 20081120)
Comment 1 Julien Cristau 2009-08-29 12:00:34 UTC
On Sat, Aug 29, 2009 at 08:48:29 -0700, bugzilla-daemon@freedesktop.org wrote:

> That's on NetBSD-5.99.15/amd64 with gcc (GCC) 4.1.3 20080704 prerelease (NetBSD
> nb2 20081120)

you don't want to build this driver on amd64…
Comment 2 Julien Cristau 2009-09-01 05:05:34 UTC
the geode is 32-bit, closing as invalid.


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.