On 2001.10.25 10:25 Daniel T. Chen wrote: > Actually I just bypassed it by putting in a #define in host.def (thanks > [EMAIL PROTECTED]) and a few extra twiddles, and it compiled and installed just > fine. Thanks. > [...] > On 25 Oct 2001, Michel [ISO-8859-1] D�nzer wrote: > > > Have you tried copying it to $ProjectRoot/lib instead?
I wonder: why is this not documented? More, why is it not possible to run a ./configure script that will detect and setup all needed things? IMHO, Answer "you should know what you are doing" is only an excuse: if a certain setup algorithm cannot be expressed via a script, there is somethin wrong with the algorithm. This also makes reproducing the results more difficult - instead of saying: I did "cvs co dri; ./configure && make World.LOG && make install" one has to explain "I did cvs co dri, run lndir ...., edited host.def; oh, I applied extra patches from xxx, then I got an error during the compilation so I copied binaries from A to B, and finally I got something". I am interested in mach64 development (apparently same reason as most people: a laptop) and could contribute some of my spare time on testing, but it seems I should start from spending my time on testing the compilation, not the driver itself... Opinions? /Pawel -- Pawel Salek, Theoretical Chemistry, SCFAB, Stockholm http://www.theochem.kth.se/~pawsa/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
