Here is a quick fix... although I'm not sure it's the right fix. It does
handle both cases of having an install dir or not though...
diff --git a/Make.common.in b/Make.common.in
index 1015dbb..af54254 100644
--- a/Make.common.in
+++ b/Make.common.in
@@ -110,7 +110,8 @@ ifeq (@enablelegacyincludepaths@,yes)
-I$(libmesh_dir)/include/reduced_basis \
-I$(libmesh_dir)/include/solvers \
-I$(libmesh_dir)/include/systems \
- -I$(libmesh_dir)/include/utils
+ -I$(libmesh_dir)/include/utils \
+ -I$(top_srcdir)/include/libmesh
endif
#
On Sun, Nov 18, 2012 at 11:20 PM, Derek Gaston <[email protected]> wrote:
> On Sun, Nov 18, 2012 at 11:02 PM, Derek Gaston <[email protected]> wrote:
>
>> However, does this build system work with the old include paths? I see
>> an include path like: -I/Users/gastdr/projects/libmesh/install/include on
>> the compile line. Is there a configure switch I need to throw to get it to
>> be -I/Users/gastdr/projects/libmesh/install/include/libmesh ??
>>
>
> Found the --enable-legacy-include-paths option... but I ended up with a
> bunch of bogus -I's like so:
>
> -I/Users/gastdr/projects/libmesh/install/include -I/include/base
> -I/include/enums -I/include/error_estimation -I/include/fe -I/include/geom
> -I/include/mesh -I/include/numerics -I/include/parallel
> -I/include/partitioning -I/include/physics -I/include/quadrature
> -I/include/reduced_basis -I/include/solvers -I/include/systems
> -I/include/utils
>
> Tracking it down now...
>
> Derek
>
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
