On Fri, 8 Feb 2013, David Knezevic wrote: > Has anyone seen this error before?
No, but I'll see if I can replicate it. I usually use gcc 4.4.4 or 4.7.2 right now, but as luck would have it Paul's built a gcc 4.6.3 module for us that I can try out. What's your configure line and your list of autodetected external libs look like? Oh, and how much RAM/swap do you have? I can't see how "make" and "make -j 8" would differ unless there was a failing malloc involved. > This issue certainly seems unrelated to libMesh, but I just wanted > to ping the list about it... Internal compiler errors are never the *fault* of libMesh, but we try to put in workarounds for them when it's not too awkward; if you look through the logs you'll see that my dof_id_type changes triggered an error in intel 12.1 that Ben had to add an extra named variable to fix; we might be able to do something similar here. --- Roy ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
