Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 180404 - x11-base/x11-drm-20060608 failed to build - size of array 'type name' is negative
Summary: x11-base/x11-drm-20060608 failed to build - size of array 'type name' is nega...
Status: RESOLVED DUPLICATE of bug 165553
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-31 02:09 UTC by Mark Kirkwood
Modified: 2007-05-31 11:29 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge.info,2.87 KB, text/plain)
2007-05-31 02:10 UTC, Mark Kirkwood
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Kirkwood 2007-05-31 02:09:19 UTC
Performed emerge -NDu world yesterday and this module would not build.

Specifically we are building with USE_FLAGS :

[ebuild   R   ] x11-base/x11-drm-20060608  VIDEO_CARDS="mach64* r128* radeon*"

Topmost error is:
CC [M]  /var/tmp/portage/x11-base/x11-drm-20060608/work/drm/linux-core/drm_stub.o
/var/tmp/portage/x11-base/x11-drm-20060608/work/drm/linux-core/drm_stub.c:51: error: size of array 'type name' is negative



Reproducible: Always

Steps to Reproduce:
1/ set VIDEO_CARDS="mach64* r128* radeon*"
2/ emerge -NDu

Actual Results:  
C [M]  /var/tmp/portage/x11-base/x11-drm-20060608/work/drm/linux-core/drm_stub.o
/var/tmp/portage/x11-base/x11-drm-20060608/work/drm/linux-core/drm_stub.c:51: error: size of array 'type name' is negative

Expected Results:  
compile sucessfully!

This is possibly due to drm module bing too old for Xorg 7.2 (thanks Google...).
Comment 1 Mark Kirkwood 2007-05-31 02:10:54 UTC
Created attachment 120735 [details]
emerge --info
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2007-05-31 11:29:50 UTC
Try with 20070314 (or preferably use the in-kernel stuff instead).


*** This bug has been marked as a duplicate of bug 165553 ***