On Mon, Jan 14, 2013 at 1:19 PM, John Peterson <[email protected]> wrote:
> On Mon, Jan 14, 2013 at 11:29 AM, Dmitry Karpeev <[email protected]> > wrote: > > Roy, > > Yes, the problem was with PETSc's makefile. It existed in the early > > versions of petsc-3.3, > > but was fixed by one of the early patches: > > > https://bitbucket.org/petsc/petsc-dev/diff/makefile?diff2=a0fe59a5123c&at=default > > I was running the latest petsc-3.3 and petsc-dev everywhere _except_ the > > machine in question, > > which prompted me to blame the machine. Without the fix above > > make -C $PETSC_DIR -s getincludedirs > > and similar will fail, if run from anywhere other than $PETSC_DIR. > > > > It looks like the problem was short lived (introduced here: > > > https://bitbucket.org/petsc/petsc-dev/diff/makefile?diff2=5f84ba60b4ac&at=default > ), > > so libmesh configure probably needn't worry about it. > > Maybe... I kind of feel like our m4 file should be a bit more > resilient to failures of this sort -- PETSc should at the least not be > enabled by configure if we can't get the proper includes and libs set > up for it. > I totally agree. And maybe log the offending output in config.log? As I said, this particular problem was very short-lived -- in between a couple of patches to petsc-3.3 -- so it is unlikely anybody will see this specific issue again, but something similar might happen. Dmitry. > > -- > John > ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 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_122412 _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
