Bug 20547 - nouveau drm doesn't build
Summary: nouveau drm doesn't build
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: git
Hardware: PowerPC Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-08 17:57 UTC by David
Modified: 2009-08-09 09:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Change ___swab32 to __swab32 and fix build on powerpc (306 bytes, patch)
2009-04-18 14:44 UTC, Andrey Gusev
no flags Details | Splinter Review

Description David 2009-03-08 17:57:43 UTC
I'm using Gentoo, nouveau overlay.  Kernel is 2.6.29-rc7-git1.  The Gentoo ebuild pulls x11-drm source from git.  I'm on powerpc.

I get this error:
  CC [M]  /var/tmp/portage/x11-base/x11-drm-99999999/work/drm/linux-core/nouveau_state.o
/var/tmp/portage/x11-base/x11-drm-99999999/work/drm/linux-core/nouveau_state.c: In function 'nouveau_load':
/var/tmp/portage/x11-base/x11-drm-99999999/work/drm/linux-core/nouveau_state.c:499: error: implicit declaration of function '___swab32'
make[2]: *** [/var/tmp/portage/x11-base/x11-drm-99999999/work/drm/linux-core/nouveau_state.o] Error 1
make[1]: *** [_module_/var/tmp/portage/x11-base/x11-drm-99999999/work/drm/linux-core] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.29-rc7-git1'
make: *** [modules] Error 2

If I change "___swab32" to "__fswab32" this compiles, as per #nouveau on irc.
Comment 1 Andrey Gusev 2009-04-18 14:44:49 UTC
Created attachment 24923 [details] [review]
Change ___swab32 to __swab32 and fix build on powerpc

I had same problem on powerpc(Debian) with kernel 2.6.29.1. I made as David did and it build.
Comment 2 Pekka Paalanen 2009-08-09 09:44:50 UTC
The swab32 function is not used anymore/currently in the nouveau DRM. Closing as fixed.

If there are build problems with the Nouveau kernel tree, file a new bug, please.


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.