Bug 8259

Summary: Siliconmotion driver won't build.... (and has no maintainer marked).
Product: xorg Reporter: Jim Gettys <jg>
Component: Driver/siliconmotionAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED FIXED QA Contact:
Severity: blocker    
Priority: highest CC: alexdeucher
Version: unspecified   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Bug Depends on:    
Bug Blocks: 6666    

Description Jim Gettys 2006-09-13 15:47:51 UTC
6666@ubuntu:~/git/xorg/driver/xf86-video-siliconmotion$ make
make  all-recursive
make[1]: Entering directory
`/home/jg/git/xorg/driver/xf86-video-siliconmotion'Making all in src
make[2]: Entering directory `/home/jg/git/xorg/driver/xf86-video-siliconmotion/src'
source='smi_accel.c' object='smi_accel.lo' libtool=yes \
        DEPDIR=.deps depmode=none /bin/sh ../depcomp \
        /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.
-I..    -I/home/jg/xorg/include/xorg -I/home/jg/xorg/include   -g -O2 -c -o
smi_accel.lo smi_accel.c
 gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/home/jg/xorg/include/xorg
-I/home/jg/xorg/include -g -O2 -c smi_accel.c  -fPIC -DPIC -o .libs/smi_accel.o
smi_accel.c: In function 'SMI_Polylines':
smi_accel.c:1103: error: 'SMI_COUGAR3DR' undeclared (first use in this function)
smi_accel.c:1103: error: (Each undeclared identifier is reported only once
smi_accel.c:1103: error: for each function it appears in.)
make[2]: *** [smi_accel.lo] Error 1
make[2]: Leaving directory `/home/jg/git/xorg/driver/xf86-video-siliconmotion/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home
Comment 1 Alex Deucher 2006-09-16 12:53:13 UTC
I'm sort of the maintainer.  Somehow a bunch of defines in regsmi.h got lost,
but the culprit looks like a commit from 2 years ago and siliconmotion has built
fine subsequently.  I'm not sure what happened, but it should be fixed in git now.

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.