It only happened once I ran the bootstrap script. I could compile without any problems before. Maybe I did not run the script correctly. The last lines in the script are these:
# # now recursively call bootstrap with the autotools in our path # export PATH=$autotools_distdir/bin:$PATH # which autoreconf # $0 Supposedly the $autotools_distdir is given by the directory where autoreconf is? Do I need to run bootstrap again or only when the message in line 151: " --> successfully installed autoreconf in $autotools_distdir/bin - please update your PATH and try again!" pops out? It doesn't pop out to me. Thanks Miguel On Tue, Jul 8, 2014 at 11:04 AM, Roy Stogner <[email protected]> wrote: > > On Tue, 8 Jul 2014, Miguel Angel Salazar de Troya wrote: > > I tried that workaround, but it didn't work. Disabling libnetcdf is a >> feasible option? >> > > I think the current version of ExodusII (which is probably our best > supported format for visualization purposes right now) depends on > netcdf. > > Someone said they could replicate this on Ubuntu 14.04; I hadn't > noticed, since I long-ago built libmesh-blessed autotools versions for > not-overwriting-the-stuff-we-have-committed purposes, but I can > disable those now and see if I can replicate the problem. > --- > Roy > -- *Miguel Angel Salazar de Troya* Graduate Research Assistant Department of Mechanical Science and Engineering University of Illinois at Urbana-Champaign (217) 550-2360 [email protected] ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
