Harden_all_packages_with_position-independent_code + guile modules
kevin at scrye.com
Sat Mar 14 19:30:08 UTC 2015
On Fri, 13 Mar 2015 19:24:58 +0100
Ralf Corsepius <rc040203 at freenet.de> wrote:
> > My conclusion is that gcc5 is at least sometimes using a lot more
> > memory than older versions.
> I haven't noticed a significant increase in memory usage in my local
> mock builds, but I haven't tried to investigate.
Yeah, me either, was just a conclusion based on the OOM.
> > Perhaps reducing smp_mflags could help?
> Dunno ;)
If you set it always to 4 do a number of scratch builds in a row work?
> > buildhw boxes have 20GB of memory and 16CPUs... so perhaps 16
> > threads is causing it to hit OOM much more often than in the past?
> > buildvm boxes have 10GB of memory, but only 4 (faster) cpus.
> > arm boxes have 4GB of memory and 4 cpus.
> Does this explain why my yesterday's scratch-builds didn't fail but
> "real" builds failed?
If it's memory related and the builders with 4 cpus always work, but
the ones on the builders with 16 cpus always fail it would.
> Does this explain why "real" builds failed yesterday but succeed
> today? Did you change something about this configuration or has
> something related to g++ changed within the last 24hrs?
> ... too many unknowns for my taste.
Such is life. ;)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the devel