On 13/03/2019 17:03, mcatanz...@gnome.org wrote:
On Wed, Mar 13, 2019 at 11:53 AM, Jakub Jelinek wrote:
calling methods on NULL pointers to objects etc.
Chromium probably does this (or, at least, did in the past). Removing
-fno-delete-null-pointer-checks could introduce Fedora-specific crash
On Wed, Mar 13, 2019 at 11:53 AM, Jakub Jelinek
wrote:
calling methods on NULL pointers to objects etc.
Chromium probably does this (or, at least, did in the past). Removing
-fno-delete-null-pointer-checks could introduce Fedora-specific crashes.
Michael
On Wed, Mar 13, 2019 at 12:49:35PM -0400, Tom Callaway wrote:
> The odd thing is that this compiler flag is hardcoded into the build by the
> upstream. I'm wondering why Fedora hits this when no one else seems to.
>
> I mean, I'm fine to disable it, because the Chromium codebase is a tomb of
> hor
The odd thing is that this compiler flag is hardcoded into the build by the
upstream. I'm wondering why Fedora hits this when no one else seems to.
I mean, I'm fine to disable it, because the Chromium codebase is a tomb of
horrors anyway, and if I have to sacrifice that flag to make it happy, so
b
On Wed, Mar 13, 2019 at 10:28:29AM -0400, Tom Callaway wrote:
> I tried removing some of the compiler flags to see if I could identify what
> might be triggering this, and removing "-fno-delete-null-pointer-checks"
> seems to make this error vanish.
-fno-delete-null-pointer-checks is certainly an
I tried removing some of the compiler flags to see if I could identify what
might be triggering this, and removing "-fno-delete-null-pointer-checks"
seems to make this error vanish.
Not sure if that helps or not, but hopefully, I can get this beast building
without it.
Thanks,
Tom
On Mon, Mar 11
On Tue, Mar 12, 2019 at 7:57 AM Christophe de Dinechin
wrote:
>
> I tried to compile your preprocessed fragment with both clang or gcc.
> Interestingly:
>
> 1) Without your command-line options, I don’t see the same error.
>
> 2) With your command-line options, I see the error with gcc, but not w
> On 11 Mar 2019, at 18:16, Tom Callaway wrote:
>
> Hi folks,
>
> I spent some time this weekend trying to get Chromium 72 building on Fedora,
> but I kept running into a C++ issue that I was not able to resolve. This
> happened with gcc-9.0.1-0.8.fc30.x86_64 and gcc-8.3.1-2.fc29.x86_64.
>
FWIW, I did. There is no fix there.
~tom
On Mon, Mar 11, 2019 at 1:20 PM Vascom wrote:
> Look at chromium-vaapi build in rpmfusion.
>
> пн, 11 мар. 2019 г., 20:17 Tom Callaway :
>
>> Hi folks,
>>
>> I spent some time this weekend trying to get Chromium 72 building on
>> Fedora, but I kept runni
On Mon, Mar 11, 2019 at 01:16:07PM -0400, Tom Callaway wrote:
> I spent some time this weekend trying to get Chromium 72 building on
> Fedora, but I kept running into a C++ issue that I was not able to resolve.
> This happened with gcc-9.0.1-0.8.fc30.x86_64 and gcc-8.3.1-2.fc29.x86_64.
Can you ple
Look at chromium-vaapi build in rpmfusion.
пн, 11 мар. 2019 г., 20:17 Tom Callaway :
> Hi folks,
>
> I spent some time this weekend trying to get Chromium 72 building on
> Fedora, but I kept running into a C++ issue that I was not able to resolve.
> This happened with gcc-9.0.1-0.8.fc30.x86_64 an
11 matches
Mail list logo
