Ben, Attached is a (possible) fix for your previous fix to enable legacy include paths (which still didn't work for me).
I'm not sure this patch is totally safe because it refers to $(top_srcdir), i.e. where the SVN checkout of libmesh resides. Do we have to assume the user can delete their $(top_srcdir) at any time and continue using the installed libmesh just fine? If so, I'm not sure what the best way to support legacy include paths would be. -- John
0001-Use-top_srcdir-instead-of-libmesh_dir-for-enabling-l.patch
Description: Binary data
------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
