First, isn't compilation is limited by the amount of virtual memory? Turning the question around, what is the point of buildd arbitrarily imposing a 4GB virtual memory limit (if it is indeed hardcoded)? If it isn't hardcoded, trying to fix scrambled spaghetti compiler code is sadly not a very practical suggestion. The issue according to the maintainer is really about why servers running the buildd service fail because of a 4GB out-of-memory error on the server. The 4GB limit means he can't build the shogun-octave package on the buildd server, so he cannot create the package for the distro. It can, however, be built with 8GB virtual memory. That's really not much memory for a complex scientific application compilation. Servers typically have much more physical (and virtual) memory than that; the average server sold last year had 18GB physical memory.
Could the 4GB limit be increased to 8GB? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090819 Title: libshogun-dev upgrade impossible - shogun-octave missing due to 4GB out-of-memory compilation error To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1090819/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
