I haven't successfully run libMesh with the Intel compilers on OS X since XCode 3.2.1. There have been numerous issues that we have traced with the release of later versions of XCode. You can search the libMesh mailing list for our discussions as we have spent a lot of time on the issue already. Perhaps some of those issues have gone away but you are sort of alone in looking for solutions. That being said I would still be interested in seeing the stack trace from running in debug mode
I would highly recommend using the Apple supplied gcc compilers when running on OS X. They are very well integrated, supported and the compile times greatly exceed what Intel can do. Cody On , Roy Stogner <[email protected]> wrote: > Not sure what's causing that (looks like a failure with dynamic > linking?) Would you try it again (make for the library and make run > for the example) with METHOD=dbg to reveal more of a stack trace? > --- > Roy > ------------------------------------------------------------------------------ > Simplify data backup and recovery for your virtual environment with > vRanger. > Installation's a snap, and flexible recovery options mean your data is > safe, > secure and there when you need it. Data protection magic? > Nope - It's vRanger. Get your free trial download today. > http://p.sf.net/sfu/quest-sfdev2dev > _______________________________________________ > Libmesh-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/libmesh-users ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
