On Wednesday 2014-11-05 12:52, Raymond Wooninck wrote:
[ 9524s] + rpmlint_logfile=/home/abuild/rpmbuild/OTHER/rpmlint.log [ 9524s] + rm -f //home/abuild/rpmbuild/OTHER/rpmlint.log [ 9524s] + ret=0 [ 9524s] + mount -n -tproc none //proc [ 9524s] + su -s /opt/testing/bin/rpmlint abuild -- --info //home/abuild/rpmbuild/RPMS/i586/chromium-beta- ffmpegsumo-39.0.2171.42-1.3.i586.rpm //home/abuild/rpmbuild/RPMS/i586/chromium- beta-39.0.2171.42-1.3.i586.rpm //home/abuild/rpmbuild/RPMS/i586/chromium-beta- desktop-gnome-39.0.2171.42-1.3.i586.rpm //home/abuild/rpmbuild/RPMS/i586/chromedriver-39.0.2171.42-1.3.i586.rpm //home/abuild/rpmbuild/RPMS/i586/chromium-beta-desktop- kde-39.0.2171.42-1.3.i586.rpm //home/abuild/rpmbuild/SRPMS/chromium- beta-39.0.2171.42-1.3.src.rpm [ 9745s] Traceback (most recent call last): [ 9745s] File "rpmlint.py", line 384, in <module> [ 9745s] File "rpmlint.py", line 169, in main [ 9745s] File "rpmlint.py", line 231, in runChecks [ 9745s] File "BinariesCheck.py", line 382, in check [ 9745s] File "BinariesCheck.py", line 179, in __init__ [ 9745s] File "Pkg.py", line 93, in getstatusoutput [ 9745s] MemoryError [ 9745s] + ret=1 [ 9745s] + cat //home/abuild/rpmbuild/OTHER/rpmlint.log [ 9745s] 1 packages and 0 specfiles checked; 0 errors, 2 warnings.
This is however only for the i586 buildhosts and I would like to know how I can resolve this ? I
I've seen something very recently, too: When Chromium is built with -ggdb3 and the default (bfd) linker in a 4GB (32-b) environment, I get a memory allocation failure in ld already - it does not even get to rpmlint. Yes, it's that big. Possible workarounds is using gcc's -gsplit-dwarf, but RPM does not support handling the so-generated files yet. [ http://www.rpm.org/ticket/879 ] -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org