-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 tom fogal wrote: > Is there any reason TLS for glX is disabled by default? Most systems > support TLS these days, do they not? Further, I'm not sure if this is > shared but my opinion is that the default configurations should cater > to the common case.
I vaguely recall there being some interaction with the X server. If Mesa is built for TLS, then the X server must also be built for TLS. If a non-TLS X server loads a TLS Mesa driver, it will fail with unresolved symbols. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkr2EOgACgkQX1gOwKyEAw8KrQCdFYN15ZgyHHYJZV/sbX3+2Qv8 hmMAoJQp4FtqMNqm0nHIX5Dl4ba07zzA =yHxS -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
