Re: Koji: virtual memory exhausted: Cannot allocate memory

2024-02-12 Thread W. Michael Petullo
>> Building the current version of my opengrm-ngram package on Koji fails
>> with the error "virtual memory exhausted: Cannot allocate memory"
>> as indicated below. This happens only for i686; all of the other
>> architectures build. Is this the fault of my package, or did something
>> change at https://koji.fedoraproject.org?
 
> the package (and its build enviroment) has grown. It fails because
> 32-bit system means max 4GB of address space for a process and ld runs
> as a single process, so it's not uncommon to use all memory for large
> C++ projects.

Thank you, Dan, for the quick response!

It had not occurred to me that the build might be hitting the
architectural limit, rather than some lower limit the build system placed
on the VM. I decided to disable the i686 build.

-- 
Mike

:wq
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Koji: virtual memory exhausted: Cannot allocate memory

2024-02-12 Thread Dan HorĂ¡k
On Mon, 12 Feb 2024 07:02:28 -0600
"W. Michael Petullo"  wrote:

> Building the current version of my opengrm-ngram package on Koji fails
> with the error "virtual memory exhausted: Cannot allocate memory"
> as indicated below. This happens only for i686; all of the other
> architectures build. Is this the fault of my package, or did something
> change at https://koji.fedoraproject.org?

the package (and its build enviroment) has grown. It fails because
32-bit system means max 4GB of address space for a process and ld runs
as a single process, so it's not uncommon to use all memory for large
C++ projects.

You can try disabling or reducing the size of debuginfo (from -g to -g1
or even -g0) to reduce the size of the *.o files. This usually helps.
Another option is to drop the i686 build per
https://fedoraproject.org/wiki/Changes/EncourageI686LeafRemoval


Dan

> 
> [...]
> libtool: link: g++ -Wl,--as-needed -std=c++17 -fno-exceptions  -fPIC -DPIC 
> -shared -nostdlib /usr/lib/gcc/i686-redhat-linux/14/../../../crti.o 
> /usr/lib/gcc/i686-redhat-linux/14/crtbeginS.o  .libs/ngram-absolute.o 
> .libs/ngram-context.o .libs/ngram-count.o .libs/ngram-count-prune.o 
> .libs/ngram-input.o .libs/ngram-kneser-ney.o .libs/ngram-list-prune.o 
> .libs/ngram-make.o .libs/ngram-marginalize.o .libs/ngram-output.o 
> .libs/ngram-shrink.o .libs/util.o   -ldl -L/usr/lib/fst -lfst -lgsl 
> -lflexiblas -L/usr/lib/gcc/i686-redhat-linux/14 
> -L/usr/lib/gcc/i686-redhat-linux/14/../../.. -lstdc++ -lm -lc -lgcc_s 
> /usr/lib/gcc/i686-redhat-linux/14/crtendS.o 
> /usr/lib/gcc/i686-redhat-linux/14/../../../crtn.o -Wl,-z,now 
> -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors 
> -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -O2 -flto=auto -g 
> -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 
> -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m32 
> -march=i686 -mtune
 =generic -msse2 -mfpmath=sse -mstackrealign -Wl,-z -Wl,relro -Wl,--as-needed 
-Wl,-z -Wl,pack-relative-relocs -Wl,-z -Wl,now 
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors 
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld 
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 
-specs=/usr/lib/rpm/redhat/redhat-package-notes -Wl,-rpath=/usr/lib/fst   
-Wl,-soname -Wl,libngram.so.1315 -o .libs/libngram.so.1315.0.0
> libtool: link: (cd ".libs" && rm -f "libngram.so.1315" && ln -s 
> "libngram.so.1315.0.0" "libngram.so.1315")
> libtool: link: (cd ".libs" && rm -f "libngram.so" && ln -s 
> "libngram.so.1315.0.0" "libngram.so")
> libtool: link: ( cd ".libs" && rm -f "libngram.la" && ln -s "../libngram.la" 
> "libngram.la" )
> virtual memory exhausted: Cannot allocate memory
> [...]
> 
> https://koji.fedoraproject.org/koji/taskinfo?taskID=113388137
> 
> -- 
> Mike
> 
> :wq
> --
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Koji: virtual memory exhausted: Cannot allocate memory

2024-02-12 Thread W. Michael Petullo
Building the current version of my opengrm-ngram package on Koji fails
with the error "virtual memory exhausted: Cannot allocate memory"
as indicated below. This happens only for i686; all of the other
architectures build. Is this the fault of my package, or did something
change at https://koji.fedoraproject.org?

[...]
libtool: link: g++ -Wl,--as-needed -std=c++17 -fno-exceptions  -fPIC -DPIC 
-shared -nostdlib /usr/lib/gcc/i686-redhat-linux/14/../../../crti.o 
/usr/lib/gcc/i686-redhat-linux/14/crtbeginS.o  .libs/ngram-absolute.o 
.libs/ngram-context.o .libs/ngram-count.o .libs/ngram-count-prune.o 
.libs/ngram-input.o .libs/ngram-kneser-ney.o .libs/ngram-list-prune.o 
.libs/ngram-make.o .libs/ngram-marginalize.o .libs/ngram-output.o 
.libs/ngram-shrink.o .libs/util.o   -ldl -L/usr/lib/fst -lfst -lgsl -lflexiblas 
-L/usr/lib/gcc/i686-redhat-linux/14 
-L/usr/lib/gcc/i686-redhat-linux/14/../../.. -lstdc++ -lm -lc -lgcc_s 
/usr/lib/gcc/i686-redhat-linux/14/crtendS.o 
/usr/lib/gcc/i686-redhat-linux/14/../../../crtn.o -Wl,-z,now 
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors 
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld -O2 -flto=auto -g 
-grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 
-fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m32 
-march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -Wl,-z -Wl,relro 
-Wl,--as-needed -Wl,-z -Wl,pack-relative-relocs -Wl,-z -Wl,now 
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors 
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld 
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 
-specs=/usr/lib/rpm/redhat/redhat-package-notes -Wl,-rpath=/usr/lib/fst   
-Wl,-soname -Wl,libngram.so.1315 -o .libs/libngram.so.1315.0.0
libtool: link: (cd ".libs" && rm -f "libngram.so.1315" && ln -s 
"libngram.so.1315.0.0" "libngram.so.1315")
libtool: link: (cd ".libs" && rm -f "libngram.so" && ln -s 
"libngram.so.1315.0.0" "libngram.so")
libtool: link: ( cd ".libs" && rm -f "libngram.la" && ln -s "../libngram.la" 
"libngram.la" )
virtual memory exhausted: Cannot allocate memory
[...]

https://koji.fedoraproject.org/koji/taskinfo?taskID=113388137

-- 
Mike

:wq
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue