Re: [chromium-freeworld] Exclude aarch64
Hi,
have you checked [1] ? I use "ulimit -n 4096" (
https://copr-dist-git.fedorainfracloud.org/cgit/sergiomb/electrons/nodejs-electron.git/tree/nodejs-electron.spec
)
but I can't install it [2]
[1]
https://fedoraproject.org/wiki/Changes/MemoryConstraintsMacros
https://src.fedoraproject.org/rpms/build-constraints-rpm-macros
[2]
mock -r fedora-35-x86_64 --install build-constraints-rpm-macros
Error: Transaction test error:
file /usr/lib/rpm/macros.d/macros.build-constraints from install of
build-constraints-rpm-macros-1-2.fc36.noarch conflicts with file from
package redhat-rpm-config-212-1.fc36.noarch
On Thu, 2022-05-26 at 12:51 +0200, Vitaly Zaitsev via rpmfusion-
developers wrote:
> On 26/05/2022 11:09, Leigh Scott wrote:
> > I have already tried limiting cpu cores.
>
> You can also try reducing the debuginfo verbosity for aarch64 and
> disable LTO:
>
> %ifnarch x86_64
> %global _lto_cflags %{nil}
> %global optflags %(echo %{optflags} | sed 's/-g /-g0 /')
> %endif
--
Sérgio M. B.
___
rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org
To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
Re: [chromium-freeworld] Exclude aarch64
Would contributing money or providing arm64 hardware for the project help?
I don't know if rpmfusion's arm builders are in a datacenter or just someone's
sbc running at their home. If it's the latter, I can certainly contribute my
own hardware. I've had it on my to-do list to learn how to setup Koji.
Thanks,
Andy
No Trees were killed in the sending of this message.
However, a large number of electrons were terribly inconvenienced.
From: Leigh Scott
Sent: Thursday, May 26, 2022 4:09 AM
To: rpmfusion-developers@lists.rpmfusion.org
Subject: Re: [chromium-freeworld] Exclude aarch64
Trying to build for aarch64 with a under powered builder isn't viable
any more.
I have already tried limiting cpu cores.
https://pkgs.rpmfusion.org/cgit/free/chromium-freeworld.git/tree/chromium-freeworld.spec#n6
I'm not willing to limit it further as it's not acceptable IMO for
builds to take longer than 14 hours +.
On 25/05/2022 20:53, Dominik 'Rathann' Mierzejewski wrote:
> On Wednesday, 25 May 2022 at 17:11, Leigh Scott wrote:
>> commit 18bbf609ff961e6a9dee32384ffd083c2f9c7b64
>> Author: Leigh Scott
>> Date: Wed May 25 16:11:03 2022 +0100
>>
>> Exclude aarch64
>>
>> chromium-freeworld.spec | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>> ---
>> diff --git a/chromium-freeworld.spec b/chromium-freeworld.spec
>> index 7f59fbe..394ab67 100644
>> --- a/chromium-freeworld.spec
>> +++ b/chromium-freeworld.spec
>> @@ -170,7 +170,7 @@ Obsoletes: chromium-vaapi < %{version}-%{release}
>> Recommends: libva-utils
>>
>> # This build should be only available to amd64
>> -ExclusiveArch: x86_64 aarch64
>> +ExclusiveArch: x86_64
> I assume this is due to
> https://koji.rpmfusion.org/koji/taskinfo?taskID=544892 failure, but why
> did it fail? I don't see any errors in the build.log. It just stops in
> the middle of the build.
>
> Regards,
> Dominik
___
rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org
To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
___
rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org
To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
Re: [chromium-freeworld] Exclude aarch64
--- Begin Message ---
On 26/05/2022 11:09, Leigh Scott wrote:
I have already tried limiting cpu cores.
You can also try reducing the debuginfo verbosity for aarch64 and
disable LTO:
%ifnarch x86_64
%global _lto_cflags %{nil}
%global optflags %(echo %{optflags} | sed 's/-g /-g0 /')
%endif
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
___
rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org
To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
--- End Message ---
Re: [chromium-freeworld] Exclude aarch64
--- Begin Message --- On 25/05/2022 21:53, Dominik 'Rathann' Mierzejewski wrote: https://koji.rpmfusion.org/koji/taskinfo?taskID=544892 failure, but why did it fail? I don't see any errors in the build.log. It just stops in the middle of the build. Killed due to OOM condition. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org --- End Message ---
Re: [chromium-freeworld] Exclude aarch64
On Thursday, 26 May 2022 at 11:09, Leigh Scott wrote: > Trying to build for aarch64 with a under powered builder isn't viable any > more. > > I have already tried limiting cpu cores. > > https://pkgs.rpmfusion.org/cgit/free/chromium-freeworld.git/tree/chromium-freeworld.spec#n6 > > I'm not willing to limit it further as it's not acceptable IMO for builds to > take longer than 14 hours +. Thanks for the explanation. Would adding more powerful aarch64 builder(s) help? Regards, Dominik -- Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
Re: [chromium-freeworld] Exclude aarch64
Trying to build for aarch64 with a under powered builder isn't viable
any more.
I have already tried limiting cpu cores.
https://pkgs.rpmfusion.org/cgit/free/chromium-freeworld.git/tree/chromium-freeworld.spec#n6
I'm not willing to limit it further as it's not acceptable IMO for
builds to take longer than 14 hours +.
On 25/05/2022 20:53, Dominik 'Rathann' Mierzejewski wrote:
On Wednesday, 25 May 2022 at 17:11, Leigh Scott wrote:
commit 18bbf609ff961e6a9dee32384ffd083c2f9c7b64
Author: Leigh Scott
Date: Wed May 25 16:11:03 2022 +0100
Exclude aarch64
chromium-freeworld.spec | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
diff --git a/chromium-freeworld.spec b/chromium-freeworld.spec
index 7f59fbe..394ab67 100644
--- a/chromium-freeworld.spec
+++ b/chromium-freeworld.spec
@@ -170,7 +170,7 @@ Obsoletes: chromium-vaapi < %{version}-%{release}
Recommends: libva-utils
# This build should be only available to amd64
-ExclusiveArch: x86_64 aarch64
+ExclusiveArch: x86_64
I assume this is due to
https://koji.rpmfusion.org/koji/taskinfo?taskID=544892 failure, but why
did it fail? I don't see any errors in the build.log. It just stops in
the middle of the build.
Regards,
Dominik
___
rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org
To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
Re: [chromium-freeworld] Exclude aarch64
On Wed, May 25, 2022 at 7:54 PM Dominik 'Rathann' Mierzejewski wrote: > I assume this is due to > https://koji.rpmfusion.org/koji/taskinfo?taskID=544892 failure, but why > did it fail? I don't see any errors in the build.log. It just stops in > the middle of the build. My guess (and it is just a guess) would be the oom killer. Chromium has a (very) long history of needing a lot of memory to compile which (on various shared builders) can get killed (with the logs just ending). ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
Re: [chromium-freeworld] Exclude aarch64
On Wednesday, 25 May 2022 at 17:11, Leigh Scott wrote:
> commit 18bbf609ff961e6a9dee32384ffd083c2f9c7b64
> Author: Leigh Scott
> Date: Wed May 25 16:11:03 2022 +0100
>
> Exclude aarch64
>
> chromium-freeworld.spec | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> ---
> diff --git a/chromium-freeworld.spec b/chromium-freeworld.spec
> index 7f59fbe..394ab67 100644
> --- a/chromium-freeworld.spec
> +++ b/chromium-freeworld.spec
> @@ -170,7 +170,7 @@ Obsoletes: chromium-vaapi < %{version}-%{release}
> Recommends: libva-utils
>
> # This build should be only available to amd64
> -ExclusiveArch: x86_64 aarch64
> +ExclusiveArch: x86_64
I assume this is due to
https://koji.rpmfusion.org/koji/taskinfo?taskID=544892 failure, but why
did it fail? I don't see any errors in the build.log. It just stops in
the middle of the build.
Regards,
Dominik
--
Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org
To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
