Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

Am Mi., 5. Jan. 2022 um 21:21 Uhr schrieb Sam James : > >> On 5 Jan 2022, at 19:18, Kai Krakow wrote: > >>> Am Mi., 5. Jan. 2022 um 19:22 Uhr schrieb Ulrich Mueller : > > [...] > >>> That applies to all parallel builds though, not only to ebuilds >>> inheriting check-reqs.eclass. By tweaking

Re: [gentoo-dev] [PATCH] kernel-2.eclass: fix minor OBOBJCOPY -> OBJCOPY typo

On 1/5/22 13:55, Emily Rowlands wrote: > Hi, > > I noticed that `NM=$(tc-getNM)` is duplicated in the changed line also, > can you fix this at the same time? > > Thanks, > Emily > > On 05/01/2022 15:59, Adrian Ratiu wrote: >> Fixes:55f5c68c01e791c7339144aadc1f20802791551e >> Suggested-by:

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

On 2022.01.05 21:10, David Seifert wrote: > On Wed, 2022-01-05 at 21:06 +, Roy Bamford wrote: > > On 2022.01.05 20:22, Sam James wrote: > > > > > > > > > > On 5 Jan 2022, at 19:02, Roy Bamford > > > wrote: > > > > > > > > Sam, > > > > > > > > Do users with FEATURES=distcc still have to

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

Roy Bamford wrote: > On 2022.01.05 20:22, Sam James wrote: >> >>> On 5 Jan 2022, at 19:02, Roy Bamford >> wrote: >>> Sam, >>> >>> Do users with FEATURES=distcc still have to opt out of this >>> MAKEOPTS clamping? >>> >> Great point! I think we could add an exemption for that and make it a >> noop

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On Wed, 05 Jan 2022, Sam James wrote: >> On 5 Jan 2022, at 08:28, Ulrich Mueller wrote: >> >> Where does this number 2 GB come from? The amount of RAM strongly >> depends on the programming language and other factors, so I don't >> believe that there's one number that can be used for

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

On Wed, 2022-01-05 at 21:06 +, Roy Bamford wrote: > On 2022.01.05 20:22, Sam James wrote: > > > > > > > On 5 Jan 2022, at 19:02, Roy Bamford > > wrote: > > > > > > Sam, > > > > > > Do users with FEATURES=distcc still have to opt out of this > > > MAKEOPTS clamping? > > > > > > > Great

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

On 2022.01.05 20:22, Sam James wrote: > > > > On 5 Jan 2022, at 19:02, Roy Bamford > wrote: > > > > Sam, > > > > Do users with FEATURES=distcc still have to opt out of this > > MAKEOPTS clamping? > > > > Great point! I think we could add an exemption for that and make it a > noop or

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

On Wed, 2022-01-05 at 09:28 +0100, Ulrich Mueller wrote: > > > > > > On Tue, 04 Jan 2022, Sam James wrote: > > > Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the > > amount of RAM available (uses amount declared as needed > > in the ebuild). Typically should be ~2GB per job. > >

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On 5 Jan 2022, at 17:51, Alec Warner wrote: > On Tue, Jan 4, 2022 at 3:03 PM Sam James wrote: >> >> On 4 Jan 2022, at 22:58, Sam James wrote: >> Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the >> amount of RAM available (uses amount declared as needed >> in the ebuild).

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On 5 Jan 2022, at 19:02, Roy Bamford wrote: > > Sam, > > Do users with FEATURES=distcc still have to opt out of this > MAKEOPTS clamping? > Great point! I think we could add an exemption for that and make it a noop or warning-only. Best, sam signature.asc Description: Message signed

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On 5 Jan 2022, at 19:18, Kai Krakow wrote: > > Am Mi., 5. Jan. 2022 um 19:22 Uhr schrieb Ulrich Mueller >: >> >>> [...] >> That applies to all parallel builds though, not only to ebuilds >> inheriting check-reqs.eclass. By tweaking MAKEOPTS, we're basically >>

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On 5 Jan 2022, at 08:28, Ulrich Mueller wrote: > >> On Tue, 04 Jan 2022, Sam James wrote: > >> Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the >> amount of RAM available (uses amount declared as needed >> in the ebuild). Typically should be ~2GB per job. > > Where does

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On 5 Jan 2022, at 19:53, Ulrich Mueller wrote: > >> On Wed, 05 Jan 2022, Florian Schmaus wrote: > >>> That applies to all parallel builds though, not only to ebuilds >>> inheriting check-reqs.eclass. By tweaking MAKEOPTS, we're basically >>> telling the user that the --jobs setting in

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On Wed, 05 Jan 2022, Florian Schmaus wrote: >> That applies to all parallel builds though, not only to ebuilds >> inheriting check-reqs.eclass. By tweaking MAKEOPTS, we're basically >> telling the user that the --jobs setting in their make.conf is wrong, >> in the first place. > Yes,

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

Am Mi., 5. Jan. 2022 um 19:22 Uhr schrieb Ulrich Mueller : > > > On Wed, 05 Jan 2022, Florian Schmaus wrote: > > > On 05/01/2022 09.28, Ulrich Mueller wrote: > >>> On Tue, 04 Jan 2022, Sam James wrote: > >>> Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the > >>> amount of RAM

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

On 05/01/2022 19.22, Ulrich Mueller wrote: On Wed, 05 Jan 2022, Florian Schmaus wrote: On 05/01/2022 09.28, Ulrich Mueller wrote: On Tue, 04 Jan 2022, Sam James wrote: Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the amount of RAM available (uses amount declared as needed in

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

On 2022.01.04 22:58, Sam James wrote: > Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the > amount of RAM available (uses amount declared as needed > in the ebuild). Typically should be ~2GB per job. > > Bug: https://bugs.gentoo.org/570534 > Signed-off-by: Sam James > --- >

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On Wed, 05 Jan 2022, Florian Schmaus wrote: > On 05/01/2022 09.28, Ulrich Mueller wrote: >>> On Tue, 04 Jan 2022, Sam James wrote: >>> Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the >>> amount of RAM available (uses amount declared as needed >>> in the ebuild). Typically

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

On Tue, Jan 4, 2022 at 3:03 PM Sam James wrote: > > > > On 4 Jan 2022, at 22:58, Sam James wrote: > > Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the > amount of RAM available (uses amount declared as needed > in the ebuild). Typically should be ~2GB per job. > > Bug:

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

I do sometimes run into OOM during emerge, but for a different reason: when firefox and webengine are built in parallel. And I'm using tmpfs for portage. These packages store lots of data in the build directory. Decreasing -j of a single package may or may not help in this case. The filled

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

On 05/01/2022 09.28, Ulrich Mueller wrote: On Tue, 04 Jan 2022, Sam James wrote: Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the amount of RAM available (uses amount declared as needed in the ebuild). Typically should be ~2GB per job. Where does this number 2 GB come from? The

[gentoo-dev] [PATCH] kernel-2.eclass: fix minor OBOBJCOPY -> OBJCOPY typo

Fixes:55f5c68c01e791c7339144aadc1f20802791551e Suggested-by: Manoj Gupta Signed-off-by: Adrian Ratiu --- eclass/kernel-2.eclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/eclass/kernel-2.eclass b/eclass/kernel-2.eclass index 865c43d3153..d1784717e41 100644 ---

Re: [gentoo-dev] [PATCH 1/2] profiles: add PPC_PAGESIZE use expand

On Tue, 2022-01-04 at 15:55 -0800, Georgy Yakovlev wrote: > Hardware can use either size, it's a built time option. > 64K is standard and is what we use by default and 99% of distros use. > 4K is more compatible with desktop applications and GPU drivers, > which often assume 4K page size. Sounds

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On Tue, 04 Jan 2022, Sam James wrote: > Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the > amount of RAM available (uses amount declared as needed > in the ebuild). Typically should be ~2GB per job. Where does this number 2 GB come from? The amount of RAM strongly depends on