[kde-edu]: kstars, compile problems, assembly and Linux kernel includes

[Scott Wheeler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Jason, et al --

KStars hasn been building here for the last couple of weeks on my SuSE 8.2 
(GCC 3.3.1) box for the last couple of weeks.

I'm seeing:

===
gcc  -ansi -W -Wall -Wchar-subscripts -Wshadow -Wpointer-arith 
- -Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -O2   
- -Wformat-sec
urity -Wmissing-format-attribute -c `test -f 'ccvt_mmx_old.S' || echo 
'./'`ccvt_mmx_old.S
ccvt_mmx_old.S:450:22: pasting "ccvt_420i_rgb24" and ":" does not give a valid 
preprocessing token
ccvt_mmx_old.S:477:22: pasting "ccvt_420i_bgr24" and ":" does not give a valid 
preprocessing token
ccvt_mmx_old.S:505:22: pasting "ccvt_420i_rgb32" and ":" does not give a valid 
preprocessing token
ccvt_mmx_old.S:532:22: pasting "ccvt_420i_bgr32" and ":" does not give a valid 
preprocessing token
ccvt_mmx_old.S:562:22: pasting "ccvt_yuyv_rgb32" and ":" does not give a valid 
preprocessing token
ccvt_mmx_old.S:589:22: pasting "ccvt_yuyv_bgr32" and ":" does not give a valid 
preprocessing token
ccvt_mmx_old.S:622:22: pasting "ccvt_420p_rgb32" and ":" does not give a valid 
preprocessing token
ccvt_mmx_old.S:666:22: pasting "ccvt_420p_bgr32" and ":" does not give a valid 
preprocessing token
ccvt_mmx_old.S:720:22: pasting "ccvt_rgb24_420p" and ":" does not give a valid 
preprocessing token
ccvt_mmx_old.S:827:22: pasting "ccvt_bgr24_420p" and ":" does not give a valid 
preprocessing token
ccvt_mmx_old.S:947:21: pasting "ccvt_420i_420p" and ":" does not give a valid 
preprocessing token
ccvt_mmx_old.S:1019:21: pasting "ccvt_420i_yuyv" and ":" does not give a valid 
preprocessing token
make[5]: *** [ccvt_mmx_old.o] Error 1
===

Generally I just fix the compile errors that I run across (and there have been 
a number of them with the recent libs that KStars has imported), but in this 
case it's x86 assembly including Linux kernel headers, which is, uhm, nasty 
to say the least.  ;-)

Might it be better to do this stuff in a way that's portable to other 
non-i386 / non-Linux platforms?

- -Scott

- -- 
Delivering chaos directly to your home since 1980:  
http://nat.org/choto.php3?p=3639
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQFAmM9hQu0ByfY5QTkRAuvsAKCuWJ10Z6Sd5/hAiS/Y1ayD4MMcigCgo7g+
fRrdOr+zZ64MYL9Ovr3DDnE=
=T9VC
-----END PGP SIGNATURE-----