On Fri, 4 Jan 2013, Roy Stogner wrote: > On Fri, 4 Jan 2013, John Peterson wrote: > >> On Fri, Jan 4, 2013 at 11:22 AM, Dmitry Karpeev <[email protected]> >> wrote: > >>> The symptoms are these: configure finds petsc, but leaves PETSCINCLUDEDIRS >>> and >>> PETSCLINKLIBS blank, which results in an >>> insufficient libmesh_optional_INCLUDES, which >>> in turn results in a failure to find petsc.h at build time. >> >> I might have broken this with my recent changes to petsc.m4... > > Yeah; I now get breakage myself when trying to build on Xubuntu with > clang, when it fails to include mpi.h. It looks like, on the path I > hit, we're correctly scarfing PETSC_CC_INCLUDES but never > incorporating that into PETSCINCLUDEDIRS?
I just pushed a fix for my own problem. It appears: The problem wasn't John's fault, just a slight change to PETSc variables when I upgraded Ubuntu which (in the CXX=clang++ scenario) our petsc.m4 wasn't prepared for. My solution won't fix Dmitry's problem. Even if somehow his configuration is leading to an empty PETSCINCLUDEDIRS which gets fixed up by now adding PETSC_CC_INCLUDES, nothing I did will lead to a fixed PETSCLINKLIBS. I'm not even sure what the *explanation* is for Dmitry's problem. Either his $PETSC_DIR/makefile is giving empty outputs for those targets, or neither it nor $PETSC_DIR/conf/variables exist as readable files on his system? At least the latter problem we should probably be testing for, but adding a final "else" to that if/elif test... --- Roy ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
