On 8/4/21 4:11 PM, Benjamin Beasley wrote:
These should work:
fedpkg mockbuild -- --define='_smp_mflags -j1'
fedpkg mockbuild -- -D '_smp_mflags -j1'
mock -r foo --rebuild bar.src..rpm --define='_smp_mflags -j1'
mock -r foo --rebuild bar.src..rpm -D '_smp_mflags -j1'
As the case is OOM rather
On Wed, Aug 4, 2021 at 8:11 AM Benjamin Beasley
wrote:
> These should work:
>
> fedpkg mockbuild -- --define='_smp_mflags -j1'
> fedpkg mockbuild -- -D '_smp_mflags -j1'
>
> mock -r foo --rebuild bar.src..rpm --define='_smp_mflags -j1'
> mock -r foo --rebuild bar.src..rpm -D '_smp_mflags -j1'
>
These should work:
fedpkg mockbuild -- --define='_smp_mflags -j1'
fedpkg mockbuild -- -D '_smp_mflags -j1'
mock -r foo --rebuild bar.src..rpm --define='_smp_mflags -j1'
mock -r foo --rebuild bar.src..rpm -D '_smp_mflags -j1'
___
devel mailing list -- de
I've finally hit a couple of packages that OOM during build with my 16GB
memory, even if I dropped out of graphical and tried from the console.
I'm assuming it's the linking so I would have to drop them considerably,
but I don't want to muck around with my ~/.rpmmacros or mock configs.
Is there a
