Re: [Mesa-dev] [PATCH] configure.ac: describe what all the LIBDRM_*REQUIRED macros mean

2017-02-03 Thread Emil Velikov
On 2 February 2017 at 17:26, Kenneth Graunke wrote: > On Thursday, February 2, 2017 9:15:47 AM PST Chad Versace wrote: >> On Thu 02 Feb 2017, Emil Velikov wrote: >> > From: Emil Velikov >> > >> > They are versions of the respective libdrm

Re: [Mesa-dev] [PATCH] configure.ac: describe what all the LIBDRM_*REQUIRED macros mean

2017-02-02 Thread Kenneth Graunke
On Thursday, February 2, 2017 9:15:47 AM PST Chad Versace wrote: > On Thu 02 Feb 2017, Emil Velikov wrote: > > From: Emil Velikov > > > > They are versions of the respective libdrm package. They are _not_ the > > version of libdrm[.so] required for driver X. > > > >

Re: [Mesa-dev] [PATCH] configure.ac: describe what all the LIBDRM_*REQUIRED macros mean

2017-02-02 Thread Chad Versace
On Thu 02 Feb 2017, Emil Velikov wrote: > From: Emil Velikov > > They are versions of the respective libdrm package. They are _not_ the > version of libdrm[.so] required for driver X. > > Doing the latter will lead to combinatoric explosion and in all fairness >

Re: [Mesa-dev] [PATCH] configure.ac: describe what all the LIBDRM_*REQUIRED macros mean

2017-02-02 Thread Manolova, Plamena
LGTM Reviewed-by: Plamena Manolova On Thu, Feb 2, 2017 at 2:32 AM, Emil Velikov wrote: > From: Emil Velikov > > They are versions of the respective libdrm package. They are _not_ the > version of libdrm[.so]

[Mesa-dev] [PATCH] configure.ac: describe what all the LIBDRM_*REQUIRED macros mean

2017-02-01 Thread Emil Velikov
From: Emil Velikov They are versions of the respective libdrm package. They are _not_ the version of libdrm[.so] required for driver X. Doing the latter will lead to combinatoric explosion and in all fairness things will likely be broken most of the time. To make