[Libmesh-users] Fwd: libMesh Make Error

[John P. <jwp...@gm...>]

---------- Forwarded message ----------
From: John Peterson <jwp...@gm...>
Date: Fri, Nov 10, 2017 at 9:19 AM
Subject: Re: [Libmesh-users] libMesh Make Error
To: Braden Frigoletto <bf...@um...>




On Fri, Nov 10, 2017 at 8:47 AM, Braden Frigoletto <bf...@um...> wrote:

> Hello,
>
> I'm trying to install libMesh on my Linux system and I'm getting an error
> when running make. It seemed to configure without any issues so I'm not
> sure why this is happening. I've attached my config.log just in case anyone
> would care to look at it. When I run make I receive the following error:
>
>   CXX      src/apps/solution_components_dbg-solution_components.o
>   CXX      src/apps/splitter_dbg-splitter.o
>   CXXLD    libmesh_dbg.la
>   CXXLD    libmesh_opt.la
>   CXXLD    fparser_parse-opt
>   CXXLD    getpot_parse-opt
>   CXXLD    amr-opt
> ./.libs/libmesh_opt.so: undefined reference to `nc_def_var_deflate'
> collect2: error: ld returned 1 exit status
> Makefile:11037: recipe for target 'getpot_parse-opt' failed
> make[1]: *** [getpot_parse-opt] Error 1
> make[1]: *** Waiting for unfinished jobs....
> ./.libs/libmesh_opt.so: undefined reference to `nc_def_var_deflate'
> collect2: error: ld returned 1 exit status
> Makefile:10959: recipe for target 'amr-opt' failed
> make[1]: *** [amr-opt] Error 1
> ./.libs/libmesh_opt.so: undefined reference to `nc_def_var_deflate'
> collect2: error: ld returned 1 exit status
> Makefile:11019: recipe for target 'fparser_parse-opt' failed
> make[1]: *** [fparser_parse-opt] Error 1
> make[1]: Leaving directory '/home/braden/Codes/libmesh'
> Makefile:29211: recipe for target 'all-recursive' failed
> make: *** [all-recursive] Error 1
>
> Any ideas on how to fix this?
>

Did you by any chance have an old libmesh build sitting around for a while
and recently do an update?

We upgraded the version of netcdf that gets distributed with libmesh and I
think I have seen errors similar to this caused by building in an existing
build directory. If that's the case, removing your build directory
completely and rebuilding should get rid of the issue.

-- 
John



-- 
John