Yes, I had to rerun bootstrap. ( I added a couple of .h and .C files, so I had to do the following:
cd include/; ./rebuild_include_HEADERS.sh cd libmesh/; ./rebuild_makefile.sh cd ../.. cd src/; ./rebuild_libmesh_SOURCES.sh cd .. ./bootstrap ./configure --with-my-preferred-options make make install ) So after this procedure the ".in" files were necessarily modified. So what you say is that I should also keep track of the changes in the ".in" files after bootstrap, right? Thanks a lot, Giorgio On Tue, Nov 11, 2014 at 3:53 PM, John Peterson <[email protected]> wrote: > On Tue, Nov 11, 2014 at 2:52 PM, John Peterson <[email protected]> > wrote: > > On Tue, Nov 11, 2014 at 2:47 PM, Giorgio Bornia > > > > Don't use -a, that commits all changed files. Just 'git commit' the > > ones you want to keep, and 'git co' the others to "revert" them. > > Sorry, "co" is my abbreviation for "checkout" > > -- > John > -- Giorgio Bornia, Ph.D. Assistant Professor Texas Tech University Department of Mathematics and Statistics 79409-1042 Lubbock, TX phone: +1 806.834.8754 fax: +1 806.742.1112 website: http://www.math.ttu.edu/~gbornia ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
