On Mon, Apr 18, 2016 at 2:48 PM, Paul T. Bauman <[email protected]> wrote:
> > > On Mon, Apr 18, 2016 at 4:38 PM, John Peterson <[email protected]> > wrote: > >> >> I'd like to blame the autotools for this. "make install" should not need >> to run mpicxx for any reason; it should just copy stuff to the >> installation >> directory. But this may not be possible with the intricacies of shared >> libraries, etc. being what they are. > > > I think it only does this if it decided that the lib needed to be rebuilt > from a change upstream in one of the source files? Just a guess. > This was running "make install" after "make" had just finished successfully. Nothing had changed. -- John ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
