Failure to compile opensaml on Amazon AWS Linux

[Rich Graves]

I foolishly thought that it would be easier to provision a fresh AWS Linux AMI than RHEL or CentOS 7. All I'd have to do is rebuild a few RPMs, right?

log4shib, xerces-c, xml-security-c, curl-openssl, and xmltooling build without incident. At this point in rmbuild --rebuild opensaml, something apparently hidden from top eats up all available RAM, exceeding 8GB. Any guesses? I guess I'll provision RHEL7 instead.

[root@ ~]# rpm -q gcc
gcc-4.8.3-3.20.amzn1.noarch

/bin/sh ../libtool --silent  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..   -pthread -Wall -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -O2 -DNDEBUG      -pthread -O2 -g -Wall -O2 -DNDEBUG -c -o saml2/metadata/impl/MetadataImpl.lo saml2/metadata/impl/MetadataImpl.cpp

top - 02:07:46 up 15 days, 23:04,  2 users,  load average: 2.83, 1.97, 1.16
Tasks:  83 total,   1 running,  82 sleeping,   0 stopped,   0 zombie
Cpu(s):  0.0%us,  2.7%sy,  0.0%ni,  0.0%id, 97.3%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:    605944k total,   599128k used,     6816k free,      204k buffers
Swap:   199996k total,   199996k used,        0k free,     3640k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
14915 root      20   0  705m 522m 1268 D  0.9 88.3   1:16.78 cc1plus
14916 root      20   0 29876  11m    0 S  0.0  2.0   0:00.17 as
15094 named     20   0  205m 7108    0 S  0.0  1.2   0:03.83 named
 1639 root      20   0  419m 2320    0 S  0.3  0.4   4:49.19 fail2ban-server
12497 root      20   0 15284  232    0 R  0.3  0.0   0:05.68 top