Roy Stogner writes: > > I wrote the following to Ben and John when I was just concerned about > seeing if we needed to update our Wiki instructions for the lonestar > supercomputer, but I'm starting to think we might be able to use a > more general fix in the library: > > > What's going on is that we're snooping PETSc's configuration for a > bunch of individual library options: $(SUPERLU_DIST_LIB), > $(BLOPEX_LIB), etc, and we're including those options in our > Make.common. Instead of trying to include every dependency one at a > time, shouldn't we be getting PETSc's whole list and using that? What > worked for me on lonestar was to change this: > > libmesh_LIBS += $(libs-PETSC) \ > $(BLOCKSOLVE_LIB) $(SPOOLES_LIB) $(HYPRE_LIB) \ > $(SUPERLU_DIST_LIB) $(UMFPACK_LIB) $(SUPERLU_LIB) \ > $(BLOPEX_LIB) $(SPAI_LIB) \ > $(BLASLAPACK_LIB) $(X11_LIB) $(MATLAB_LIB) \ > $(libmesh_FLIBS) > > Into this: > > libmesh_LIBS += $(libs-PETSC) \ > $(PACKAGES_LIBS) \ > $(libmesh_FLIBS) > Good find! I've spent some time staring at petscconf files without seeing PACKAGES_LIBS. It seems to be supported back through at least PETSC 2.3.1, and as long as their isn't a Makefile namespace clash this seems like a good solution.
-J ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
