Thank you John, I guessed as much. I'm involved in a few things (one of which requires exodusii inside PETSc) and it would have been nice to use the same PETSc arch for all of them. But I can compile a libMesh specific PETSc without NetCDF.
Best, Ata On Tue, Jul 5, 2016 at 3:33 PM, John Peterson <[email protected]> wrote: > > > On Tue, Jul 5, 2016 at 12:57 PM, Ata ollah Mesgarnejad < > [email protected]> wrote: > >> Apologies forgot to CC the list. >> > > > You are explicitly doing --download-netcdf=1 when building PETSc. Since > this is the first I'm seeing it, what are you using in PETSc that requires > NetCDF? > > The linking error is probably caused because libmesh is using the NetCDF > header files that come with libmesh, but subsequently linking with the > NetCDF that you built in PETSc. > > We could probably fix this in a manner similar to the way we use PETSc's > Metis/ParMetis when it is available, but it will require some testing to > get right, and will definitely be an "odd" build configuration that not > many people use/may regress without warning. > > -- > John > -- Best, Ata ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
