compiling new drm drivers

Eric <[email protected]>
Newsgroups gmane.comp.video.dri.user
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

im sorry to bother with such an odd question but while following the
DRI-wiki on how to built an up to date driver I encountered some
problem, maybe.

While following "1.4. Building Mesa 3D drivers on Linux" i get a bunch
of errors like
[code]
line 73): cannot find include file "stdarg.h"
        not in ./stdarg.h
        not in ../../../include/stdarg.h
        not in ../../../include/GL/internal/stdarg.h
        not in ../../../src/mesa/main/stdarg.h
        not in ../../../src/mesa/glapi/stdarg.h
        not in ../../../src/mesa/drivers/dri/common/stdarg.h
        not in /usr/local/include/stdarg.h
        not in /usr/local/include/drm/stdarg.h
        not in /usr/X11R6/include/stdarg.h
        not in /usr/include/stdarg.h
[/code]
this is the same for maybe 6 to 10 files.
afterwards he seems to compile anyway. in the end i have 3 versions of
libGL in the Mesa/lib. the first instruction of 1.6 says to "cp
lib/*_dri.so /usr/X11R6/lib/modules/dri/" but i lack any file fitting
the pattern "*_dri.so" which I guess is because of the errors above ?

I hope I made my question clean and sorry if the question is too odd.
thanks a lot for your time, Eric.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFa0PdtqT/C3SDZicRApOsAKCvVR3LEbzU4zJRbzCjfQPr4b5GEwCfY1CJ
9pxy6Yn7x+ea4qdrv4FWP8A=
=4m//
-----END PGP SIGNATURE-----


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.