I tried that workaround, but it didn't work. Disabling libnetcdf is a feasible option?
On Mon, Jul 7, 2014 at 5:15 PM, Roy Stogner <[email protected]> wrote: > > On Mon, 7 Jul 2014, Miguel Angel Salazar de Troya wrote: > > I ran the bootstrap script (just run it once) and it could detect the new >> files, but I got an error during the compilation: >> /usr/bin/ld: src/apps/meshid_opt-meshid.o: undefined reference to symbol >> 'nc_close' >> /usr/local/lib/libnetcdf.so.7: error adding symbols: DSO missing from >> command line >> collect2: error: ld returned 1 exit status >> >> I have netcdf enabled in the configuration. I didn't have this problem >> before I ran the bootstrap script. I'm sorry not to provide more details, >> but I've no idea why this error happens because I know very little about >> automake or autoconf tools and I could not find much on the internet. i >> think it's a problem of dependencies, but that's all. >> > > I once saw this happen (libtool started looking for libnetcdf in > /usr/local/lib rather than the proper directory) but I no longer > recall what the diagnosis or fix was. We ought to find a permanent > fix, but my current workaround is to always build outside the source > directory and to start from an empty build directory if I ever suspect > something might misbehave. > --- > 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
