On 3/9/18 6:53 pm, Alexander Larsson wrote:
On Mon, Sep 3, 2018 at 10:41 AM Alexander Larsson wrote:
On Fri, Aug 31, 2018 at 4:05 PM Emil Velikov wrote:
Valid point - I forgot about that.
A couple of ideas come to mind:
- static link LLVM (Flatpak already does it)
No LLVM changes
On 3/9/18 6:53 pm, Alexander Larsson wrote:
On Mon, Sep 3, 2018 at 10:41 AM Alexander Larsson wrote:
On Fri, Aug 31, 2018 at 4:05 PM Emil Velikov wrote:
Valid point - I forgot about that.
A couple of ideas come to mind:
- static link LLVM (Flatpak already does it)
No LLVM changes
On Mon, Sep 3, 2018 at 10:41 AM Alexander Larsson wrote:
>
> On Fri, Aug 31, 2018 at 4:05 PM Emil Velikov wrote:
> >
> > Valid point - I forgot about that.
> >
> > A couple of ideas come to mind:
> > - static link LLVM (Flatpak already does it)
> > No LLVM changes needed.
> >
> > - shared link
On Fri, Aug 31, 2018 at 4:05 PM Emil Velikov wrote:
>
> Valid point - I forgot about that.
>
> A couple of ideas come to mind:
> - static link LLVM (Flatpak already does it)
> No LLVM changes needed.
>
> - shared link LLVM
> LLVM add -Wl,--build-id=sha1
As a very very simple workaround, can
On Fri, Aug 31, 2018 at 4:05 PM Emil Velikov wrote:
>
> On 31 August 2018 at 14:36, Timothy Arceri wrote:
> > On 31/08/18 21:07, Emil Velikov wrote:
> >>
> >> On 31 August 2018 at 11:37, Timothy Arceri wrote:
> >>>
> >>> On 31/08/18 20:10, Emil Velikov wrote:
>
>
> Hi Timothy,
>
On 31 August 2018 at 14:36, Timothy Arceri wrote:
> On 31/08/18 21:07, Emil Velikov wrote:
>>
>> On 31 August 2018 at 11:37, Timothy Arceri wrote:
>>>
>>> On 31/08/18 20:10, Emil Velikov wrote:
Hi Timothy,
On 31 August 2018 at 10:57, Timothy Arceri
wrote:
>
On 31/08/18 21:07, Emil Velikov wrote:
On 31 August 2018 at 11:37, Timothy Arceri wrote:
On 31/08/18 20:10, Emil Velikov wrote:
Hi Timothy,
On 31 August 2018 at 10:57, Timothy Arceri wrote:
On 31/08/18 19:40, Bas Nieuwenhuizen wrote:
+TImothy
On Fri, Aug 31, 2018 at 11:32 AM
On Fri, Aug 31, 2018 at 11:57 AM Timothy Arceri wrote:
>
> On 31/08/18 19:40, Bas Nieuwenhuizen wrote:
> We depend on build timestamps of the mesa/llvm binaries when generating
> the sha for cache items. So if flatpak results in two versions of mesa
> having the same timestamp then there is
On 31 August 2018 at 11:37, Timothy Arceri wrote:
> On 31/08/18 20:10, Emil Velikov wrote:
>>
>> Hi Timothy,
>>
>> On 31 August 2018 at 10:57, Timothy Arceri wrote:
>>>
>>> On 31/08/18 19:40, Bas Nieuwenhuizen wrote:
+TImothy
On Fri, Aug 31, 2018 at 11:32 AM Alexander
On 31/08/18 20:10, Emil Velikov wrote:
Hi Timothy,
On 31 August 2018 at 10:57, Timothy Arceri wrote:
On 31/08/18 19:40, Bas Nieuwenhuizen wrote:
+TImothy
On Fri, Aug 31, 2018 at 11:32 AM Alexander Larsson
wrote:
Hi, I'm the developer behind flatpak (https://flatpak.org/) and we've
Hi Timothy,
On 31 August 2018 at 10:57, Timothy Arceri wrote:
> On 31/08/18 19:40, Bas Nieuwenhuizen wrote:
>>
>> +TImothy
>>
>> On Fri, Aug 31, 2018 at 11:32 AM Alexander Larsson
>> wrote:
>>>
>>>
>>> Hi, I'm the developer behind flatpak (https://flatpak.org/) and we've
>>> recently run into
On 31/08/18 19:40, Bas Nieuwenhuizen wrote:
+TImothy
On Fri, Aug 31, 2018 at 11:32 AM Alexander Larsson wrote:
Hi, I'm the developer behind flatpak (https://flatpak.org/) and we've
recently run into some issues with the mesa shader cache. Flatpak has
a app/runtime split where the runtime is
+TImothy
On Fri, Aug 31, 2018 at 11:32 AM Alexander Larsson wrote:
>
> Hi, I'm the developer behind flatpak (https://flatpak.org/) and we've
> recently run into some issues with the mesa shader cache. Flatpak has
> a app/runtime split where the runtime is shared between app and
> provides /usr.
Hi, I'm the developer behind flatpak (https://flatpak.org/) and we've
recently run into some issues with the mesa shader cache. Flatpak has
a app/runtime split where the runtime is shared between app and
provides /usr. The runtime contains a version of mesa, but this can be
overridden by runtime
14 matches
Mail list logo
