[Dri-devel] Why revive R200_NO_TCL?

Hi, after Dieter's last mail I wonder why the environment variable R200_NO_TCL was revived. I didn't notice this before so I assume this slipped in during the move to Mesa CVS. Since environment variables can be used to override configuration options this is really no longer necessary. You can use

Re: [Dri-devel] Why revive R200_NO_TCL?

Am Samstag, 13. Dezember 2003 23:43 schrieb Felix Kühling: > Hi, > > after Dieter's last mail I wonder why the environment variable > R200_NO_TCL was revived. I didn't notice this before so I assume this > slipped in during the move to Mesa CVS. Since environment variables can > be used to override

Re: [Dri-devel] Why revive R200_NO_TCL?

On Sun, 14 Dec 2003 15:11:06 +0100 Dieter Nützel <[EMAIL PROTECTED]> wrote: > Am Samstag, 13. Dezember 2003 23:43 schrieb Felix Kühling: > > Hi, > > > > after Dieter's last mail I wonder why the environment variable > > R200_NO_TCL was revived. I didn't notice this before so I assume this > > slip

Re: [Dri-devel] Why revive R200_NO_TCL?

Felix Kühling wrote: Hi, after Dieter's last mail I wonder why the environment variable R200_NO_TCL was revived. I didn't notice this before so I assume this slipped in during the move to Mesa CVS. Since environment variables can be used to override configuration options this is really no longer n