Hi guys, Good news -- the system admins are installing 2.8.4 on all the government Cray machines!
Bad news -- I can't actually get anything to work. I pulled the git repo version and built the master branch because of what David pointed out. However, I cannot figure out how to make it actually link. I get errors on all my executables saying ftn-2191 crayftn: ERROR in command line "ynamic" is an invalid argument to the "-r" option. How can I get it to drop the -rdynamic option? Tim ----- Original Message ----- From: "David Partyka" <[email protected]> To: "Eric Noulard" <[email protected]> Cc: [email protected], [email protected] Sent: Saturday, March 5, 2011 12:03:40 PM Subject: Re: [CMake] Cmake with Cray Fortran FYI, if you want to build static on cray, Brad just checked in a fix into CMake yesterday that addresses -Bdynamic link flags showing up in the link line even though you're trying to build static, often resulting in your executable prefering to link against shared system libraries rather than static. This was causing issues linking static while building ParaView on Jaguar. http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5abfb571843dba949e010f3b2840d8882d0f3d73 On Sat, Mar 5, 2011 at 11:21 AM, Eric Noulard < [email protected] > wrote: 2011/3/5 Tim Gallagher < [email protected] >: > Eric, > > Excellent! Thanks! > > I don't know a whole lot about CMake (yet) -- would it be possible to make > older versions aware of the compiler if I were to package only the updated > files rather than install my own version of CMake? In other words, was it > something simple like changing the CMakeFortranCompilerId.F file and if so, > could I tell another version of CMake to use my own copy of that file? I don't know I am not the author of the fix, I think Brad King was the one who did this, may be he will answer that. > It would be a lot easier if I only had to make our users put a few extra > files somewhere than have them all install their own version of CMake in > their home directories on all these Cray machines. May be deploying CMake 2.8.4 globally on each machine and set up appropriate module would even be easier for the users? Or may be this is not an option because you don'thave administrative privilege on those machines? -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
