Hi John.

On 06/15/2014 08:43 PM, John Reiser wrote:
>> These compilations have been particularly annoying because it was
>> nearly impossible to compile on my PC without blocks dependent by
>> *high* memory usage.
> 
> How much RAM and swap and free space does the build machine have?
> ("sed 5q  < /proc/meminfo;  cat /proc/swaps;  df -h")

$ sed 5q  < /proc/meminfo;  cat /proc/swaps;  df -h
MemTotal:        4013076 kB
MemFree:          530220 kB
MemAvailable:    2846052 kB
Buffers:          169788 kB
Cached:          2235416 kB
Filename                                Type            Size    Used    Priority
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda6        96G   54G   38G  59% /
devtmpfs        2.0G     0  2.0G   0% /dev
tmpfs           2.0G  152K  2.0G   1% /dev/shm
tmpfs           2.0G  952K  2.0G   1% /run
tmpfs           2.0G     0  2.0G   0% /sys/fs/cgroup
tmpfs           2.0G   24K  2.0G   1% /tmp
/dev/sda5       477M  252M  196M  57% /boot


> 
> The BuildRequires of coin-or-lemon-devel seems to be not yet available in f20,
> so "rpmbuild -bc seqan.spec" fails. 

coin-or-lemon is still in f20 updates-testing repos; considering that my
PC haven't sufficient RAM, I had to base RPM building tests only on Copr
(http://copr-be.cloud.fedoraproject.org/results/sagitter/OpenMS/fedora-20-x86_64/seqan-1.4.1-2.fc20/build.log).

> Using the seqan-src-1.4.1.tar.gz
> that is named in https://bugzilla.redhat.com/show_bug.cgi?id=1105730
> and invoking by hand the 'cmake' command from seqan.spec, then a
> plain "make -k" using -O2 [but no "-j" parallelization], I compiled 
> all-but-one
> of the source files.  On razers3/razers.cpp, the complaint "OpenMP not found"
> caused failure.  Perhaps OpenMP should be a requirement?

It's not explicitly required by upstream, but probably it's necessary.

> 
> On my 3.4GHz box with 8GB RAM, compiling finished in less than 30 minutes.
> While compiling, I watched the display from /usr/bin/top.  On pair_align.cpp
> the VIRT for c++ reached just under 3000000 (3M * 1KB ==> 3GB).
> Memory usage for other files seemed to be 500MB (VIRT 500000) or less.
> So you need 3GB of RAM for g++ on pair_align.cpp, which means
> 4GB RAM on the box.  If you don't have 4GB of RAM then you must have
> swap space (paging space) to make up the difference; and compiling
> that file will take much longer (estimate: 10 to 20 times as long)
> because of the paging.
> 

So my RAM is not adequate. Even if, maybe, not even koji seems to can
build pair_align.cpp keeping all RPM_OPT_FLAGS.

-- 
Antonio Trande

mailto: sagitterATfedoraproject.org
http://www.fedoraos.worpress.com
https://fedoraproject.org/wiki/User:Sagitter
GPG Key: D400D6C4
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Reply via email to