On 07-Jun-99 Keith Whitwell wrote:
>> I believe that you can, as long as your binutils can cope.
>> > and do the
>> > test at runtime to decide which ones to activate?
...
> I'm a bit naive on the make options as I usually hack my own makefiles.
> I was really referring to the need for the seperate defines for 3dnow,
> x86 and mmx. I think a better approach would be to compile everything
> we are capable of & do the checks at runtime. There are '3dnow' targets
> in the toplevel makefile for example - I'd be happy to see this
> disappear. I haven't checked the behaviour of the new autoconf scripts
> either, so all in all I really don't have much original information to
> add to this discussion...
My configure script automatically enables 3Dnow and MMX support
on all x86 chips. You can disable assembler code with --enable-x86=off,
3Dnow support with --enable-3dnow=off and MMX support
with --enable-mmx=off.
Thomas Tanner -----------------------------------------
email: tanner@(ffii.org|gnu.org|ggi-project.org|gmx.de)
web: http://home.pages.de/~tanner
GGI/Picasso: http://picasso.ffii.org
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
