Custom Search
-- Mengjuei Hsieh, Molecular Biology & Biochem, Univ. of California Irvine. > From: Ben Roberts <ben.roberts.geek.nz> > Reply-To: AMBER Developers Mailing List <amber-developers.ambermd.org> > Date: Tue, 25 Jan 2011 09:29:44 -0500 > To: AMBER Developers Mailing List <amber-developers.ambermd.org> > Subject: [AMBER-Developers] Dealing with compiler warnings, etc. > > Hi all, > > I've been quietly, off and on, chipping away at a few of the compiler warnings > in the Amber code - building it with "-Wall" (for C/C++ code) and "-warn all" > (for Fortran code) and seeing what I get. Understandably, there are a lot of > complaints, some of which (in the case of the Fortran code) cause the > compilation to stop (mismatched variable types, etc). But trying to sort all > that out - which involved messing around with variable declarations, > assumed-shape vs. assumed-size arrays, and so forth - seemed better done in a > dedicated branch than in my regular development branch. > > So I started a branch for that purpose, based off the config-devel branch > (whose original purpose was for improving the passing of compiler flags; this > is now in the master). That branch is called "remove-warnings", for want of a > better name. It's generally available for anyone who feels like tinkering in > the oodles of spare time I'm sure we all have (*wry grin*). > > As a side note, my understanding is that the branch "config-devel" is now > surplus to requirements. But before I blow it away, is anyone else doing > anything in there? > > Cheers, > Ben > > -- > For greater security, I support S/MIME encryption. > > > _______________________________________________ > AMBER-Developers mailing list > AMBER-Developers.ambermd.org > http://lists.ambermd.org/mailman/listinfo/amber-developers _______________________________________________ AMBER-Developers mailing list AMBER-Developers.ambermd.org http://lists.ambermd.org/mailman/listinfo/amber-developersReceived on Fri Apr 01 2011 - 20:30:03 PDT