On 30/05/15 20:31, Paul Eggert wrote: > Daniel Pocock wrote: >> Can this be handled any better by autotools or is it a g++ problem >> exclusively? > > No, it's a problem that in principle affects every program. If you > don't have enough memory, your programs won't run. > Well, some programs give a clear error when they need more RAM and the user buys the RAM or changes their virtual machine settings In this case, two things went wrong: a) the g++ output was really obscure, no suggestion that it was a RAM problem b) the output of every second g++ invocation is redirected to /dev/null by libtool, so the error doesn't always appear at all _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf