On Nov 19, 2012, at 11:32 AM, Roy Stogner <[email protected]> wrote:
> > On Fri, 16 Nov 2012, Kirk, Benjamin (JSC-EG311) wrote: > >> In the meantime please contact me before you get too frustrated with >> automake - it is usually easy to do something if you do it the >> 'automake way.' > > As long as we're dogpiling you with bug reports: > > > There was a small issue with trilinos.m4 which led to > config_summary.m4 erroneously reporting that it found trilinos; it > should be fixed now but since my autotools are a touch out of date I > left it to you to check in any updated configure, .in files. Thanks, I'll add that momentarily, along with two utility scripts: ./src/rebuild_libmesh_la_SOURCES.sh ./include/rebuild_include_HEADERS.sh which automate the generation of the source file lists. Should probably be extended to automake the svn add as well, then adding new sources will actually be less painful than before. > I'm seeing failures to compile fparser, looking like: > > GEN fp_opcode_add.inc > ln: failed to create symbolic link `fp_opcode_add.inc': File exists > > on multiple systems. Building with --disable-fparser works, but > eventually I'm going to want to use that again. ;-) > --- > Roy Is this a clean trunk or updated on top of an old one? The reason I ask is because contrib/fparser/extrasrc/fp_opcode_add.inc should not exist and is not checked in - it is either a built source if you want to build the fparser development version, or a symlink when building the release version. In either case it should be removed by make clean and not exist for a clean checkout, and the symlink should work. -Ben ------------------------------------------------------------------------------ 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
