[Mesa-dev] [RFC libdrm 0/2] Replace the build system with meson

[Timothy Arceri]

On 29/03/17 03:59, Emil Velikov wrote:
> Hi Chad,
>
> On 24 March 2017 at 20:44, Chad Versace <chadversary at chromium.org> wrote:
>> On Tue 21 Mar 2017, Matt Turner wrote:
>>> On Mon, Mar 20, 2017 at 12:39 PM, Emil Velikov <emil.l.velikov at gmail.com> wrote:
>>>> On 20 March 2017 at 18:30, Matt Turner <mattst88 at gmail.com> wrote:
>>>>> On Mon, Mar 20, 2017 at 6:55 AM, Emil Velikov <emil.l.velikov at gmail.com> wrote:
>>
>>>>>> These projects have been getting closer to upstream and "forcing" the
>>>>>> extra obstacle is effectively giving them the middle finger.
>>>>>
>>>>> No. Requiring us to compile with a 10 year old GCC is giving a middle finger.
>>>>>
>>>> Can we stop with the GCC thing ? Can we point to a place where we want
>>>> to use feature A introduced with GCC B and we don't ?
>>>
>>> Are you freaking serious?!
>>>
>>> This happens *all* the time. It happened like two days ago with commit
>>> 28b134c75c1fa3b2aaa00dc168f0eca35ccd346d. I'm sure it probably
>>> happened at least once in the previous month, and every month before
>>> that.
>>
>> More examples:
>>
>>     - Jason and I wanted to use C11 generic expressions (that's what the
>>       C11 spec calls them) in anvil, but old GCC => !C11.
>>
> [snip]
>>
>>         freenode.#dri-devel.log-2017-03-16 11:07:12 | imirkin_ | vulkan/anv_device.c:697:4: error: initializer element is not constant
>>         freenode.#dri-devel.log-2017-03-16 11:07:12 | imirkin_ | .minImageTransferGranularity = (VkExtent3D) { 1, 1, 1 },
>>         freenode.#dri-devel.log-2017-03-16 11:07:23 | imirkin_ | anyone seen this? i'm on HEAD
>>         freenode.#dri-devel.log-2017-03-16 11:13:50 | vsyrjala | yep. gcc-4.9 strikes again?
>>         freenode.#dri-devel.log-2017-03-16 11:14:54 | imirkin_ | i'm definitely using gcc-4.9
>>         freenode.#dri-devel.log-2017-03-16 11:15:16 | vsyrjala | that '(VkExtent3D)' looks very much pointless there
>>         freenode.#dri-devel.log-2017-03-16 11:15:56 | imirkin_ | 4.9.4 as it happens, which is the "stable" gcc on gentoo
>>         freenode.#dri-devel.log:2017-03-16 11:18:04 | vsyrjala | looks like chadv broke it
>
> As mentioned elsewhere - if major stakeholders of $driver want to bump
> the requirement, please do.
> As an example: st/nine requires GCC 4.6 and st/clover GCC 4.7 for a
> very long time.

That seems fine for optional state trackers but seems like a bad idea to 
encourage that for major drivers. It's likely to lead to features being 
used in common code.

I'm not actually against this, just pointing out the obvious.

Hopefully VMWARE will migrate to something newer at some stage. That 
seems to be the major blocker at this point in time.