Good question! In this case I built the entire software stack from MPICH2 on up so there should be minimal cross linking going on. However there most likely are some lower level system libraries that are provided by Apple that may be the case of the problem. I really need to do a more thorough look through the new files and see what candidates might be causing the problem but I'd like to watch the forums a bit over the next few days to see if others are experiencing similar issues. This error is easily reproduced. I deleted my libMesh directory and started from a clean build and ran into the error consistently with the new version using no external (excluding contrib) libraries. I'll keep you posted if I learn anything new.
Cody On May 3, 2010 2:19pm, Roy Stogner <[email protected]> wrote: > Copying this to libmesh-users in case anyone there gets bitten by it. > Thanks for the warning! > So this looks like possibly an ABI problem? Objects built with > XCode's custom g++ version not playing nicely when linked against > objects built with icpc? > --- > Roy > On Mon, 3 May 2010, Cody Permann wrote: > Apple posted an update to XCode late last week (3.2.2) which I installed > on Friday afternoon on my Mac workstation. After the update our libMesh > based applications started throwing runtime errors (Seg. Faults). As a > troubleshooting step, I started disabling libMesh external dependancies > and running the examples inside of libMesh but received runtime errors > there as well. There is some sort of negative reaction between recent > Intel compilers and the new XCode Application but I haven't seen anything > specific popping up in the forums yet. In fact the release notes for > XCode specifically say "better support for the Intel icc compiler > family". At one place on the Intel site, one of the developers said they > had been running the Intel regression tests against XCode and hadn't seen > any problems yet. > Full disclosure: I am not running the very latest build of the Intel > Compilers since we are in the process of renewing our license. Our build > is recent but not the very latest. There may be a bad interaction between > our build and the Apple build but I just wanted to toss this apparent > problem out there in case anybody else runs into it. For now I have > reverted back to XCode 3.2.1 which has fixed the problem. > Cody > ------------------------------------------------------------------------------ > _______________________________________________ > Libmesh-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/libmesh-devel ------------------------------------------------------------------------------ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
