For all details see: http://bugs.mercury.csse.unimelb.edu.au/view.php?id=31 Reproducible: Always
(In reply to comment #0) > For all details see: http://bugs.mercury.csse.unimelb.edu.au/view.php?id=31 I can't because it shows nothing without login. Please post the relevant errors and emerge --info output here.
Created attachment 138140 [details] build.log.bz2 build log
Created attachment 138142 [details] emerge_start.log.bz2 ulimit info and building start not included into build.log.bz2
Created attachment 138144 [details] environment.bz2 environment dump (by emerge)
Created attachment 138146 [details] config.log.bz2 log of configure (autoconf)
During building process of v0.13.1 on amd64-compatible platform there is stage with building modules (Internals) and at that moment there is huge memory usage which finally produce out of memory (tried at 2 GB ram + 4 GB swap). As contrary to that 32-bit version is built normally on the same platform. You can find building process log in attachment build.log.bz2. At this time I've limited memory usage to 1.5 GB to avoid breaking of other processes. Please see emerge_start.log.bz2 for info. config.log.bz2 - is copied and compressed from topdir. juliensf>The entire configuration process looks very odd for that type of machine. juliensf>My guess is that it is something to do with the way the Gentoo package is running the build process. juliensf>I think this should be reported as a bug in the Gentoo Mercury package, via bugs.gentoo.org.
Thanks. These semi-public issues trackers really suck. :/
Thanks for the bug report. It looks like mcc will build but not run correctly with gcc optimizations provided by gcc-4.2.x. Dialing back CFLAGS to -O0 works but isn't really ideal. :-(
Created attachment 158729 [details] building with gcc-4.3.1 CFLAGS='-O3 -march=core2 -mtune=core2 -msse -msse2 -msse3 -maccumulate-outgoing-args -minline-all-stringops -pipe'
I've committed mercury-0.13.1-r2 to CVS. This has an upstream fix for mmc on 64bit systems. Keri
