From: edgar <edg...@cr...> - 2021-03-23 23:09:18
|
On 2021-03-23 16:07, John Peterson wrote: > Hi Edgar, > > Sorry for the lack of reply. I did get your patch, but did not have a > chance to try it out yet. Should this be applied on top of the changes > in > the related PR (https://github.com/libMesh/libmesh/pull/2602)? On > libmesh > master? Also, you mentioned: > >> "and needs further fixing" > > Any hints as to what else might need to be changed? Hi John. Further apologies for missing the discussion (https://github.com/libMesh/libmesh/pull/2388). I thought that it was abandoned. What I can report about https://github.com/libMesh/libmesh/pull/2602 is this: With the b91a8d3c5 commit of libMesh, I removed the line where my patch is applied, then ran =autoconf=, and omitted the =sed= line which changes =configure=. The summary is that it still uses =contrib/netcdf= for me (https://bitbin.it/pVrS2245/). I do have =--enable-netcdf= --with-netcdf=/usr/include --with-netcdf-lib=/usr/lib= as configuration flags. I _am_ able to compile with my local netcdf if 1. I apply the patch 2. Run =autoconf= 3. Run the =sed= line on =configure= After I read https://github.com/libMesh/libmesh/wiki/Updating-configure-tests%2C-Makefiles%2C-etc and it seems that libMesh's building stack creates a new an error with TIMPI configure: error: libmesh/contrib/timpi/configure failed for contrib/timpi ==> ERROR: A failure occurred in build(). Aborting... In any case, you can see the final =configure= and my =netcdf.m4= here: https://notabug.org/broncodev/libMesh.git (my internet connection could be better an it is uploading as I click Send) |