> On Feb 7, 2014, at 8:31 AM, "Kirk, Benjamin (JSC-EG311)" 
> <benjamin.k...@nasa.gov> wrote:
> 
> In file included from 
> /home0/bkirk/codes/install/libmesh/v0.9.3-rc2/include/boost/pool/pool.hpp(12),
>                 from 
> /home0/bkirk/codes/install/libmesh/v0.9.3-rc2/include/libmesh/pool_allocator.h(27),
>                 from /tmp/pool_allocator.h.aisurLIV1S.cxx(1):
> /home0/bkirk/codes/install/libmesh/v0.9.3-rc2/include/boost/config.hpp(35): 
> catastrophic error: cannot open source file "boost/config/compiler/intel.hpp"
>  #  include BOOST_COMPILER_CONFIG
>                                  ^
> I just got this doing a ‘make distcheck’ - comparing our contrib/boost to 
> /opt/local/… from macports is illustrative:
> 
> $ ls contrib/boost/include/boost/config/compiler/
> gcc.hpp
> 
> $ ls /opt/local/include/boost/config/compiler/
> borland.hpp     compaq_cxx.hpp  greenhills.hpp  mpw.hpp         sunpro_cc.hpp
> clang.hpp       cray.hpp        hp_acc.hpp      nvcc.hpp        vacpp.hpp
> codegear.hpp    digitalmars.hpp intel.hpp       pathscale.hpp   visualc.hpp
> comeau.hpp      gcc.hpp         kai.hpp         pgi.hpp
> common_edg.hpp  gcc_xml.hpp     metrowerks.hpp  sgi_mipspro.hpp
> 
> John, do you have the missing headers for the same version of Boost you 
> recently upgraded us to?

They are just from 1.55.0. 

I'm pretty sure this is due to me using my compiler (GCC) to generate 
dependencies instead of bc... There's no reason it would need to pull in 
intel.hpp.

I'm baby sitting right now but I can try to fix this later today...




------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to