Comments (5)
You're reporting this in the wrong place (we didn't write those build scripts and don't support things we didn't write), but if you're looking for a workaround for your own sake then surely the answer is
Install m4 and try again.
libMesh doesn't require m4 to configure itself (I just tested this with a configure --disable-netcdf
on a system with m4 uninstalled) but if NetCDF does and if you want NetCDF (either because you need ExodusII support or because you also don't want to futz with someone else's build scripts) then you're going to need m4.
from libmesh.
Do you plan to add cmake support ?
from libmesh.
No; I've been disappointed with cmake every time I've interacted with it (including recently), and I definitely don't want to employ it myself. Autotools is of course also disappointing, but disappointing in different ways which we mostly manage to work around.
(the above might be unfair to cmake - it's quite possible that the core software is fine but the various packages I've run into have been flaky - but part of what I like about autotools is the abundance of pre-existing much-less-flaky archives)
I do need to look at more recently developed build systems one of these days, though. I heard good things about https://bazel.build/ not long ago. Even if there were no downsides I couldn't imagine switching over any time soon, though; there's a bit of a chicken-and-egg problem with making that large of a change to a system we don't have a lot of experience with.
from libmesh.
Sadly, CMake seems to be the most widely accepted hot garbage for building C++ libraries and applications these days. It's slowly improving, but it's a massive PITA to do even slightly atypical things. But it's probably possible, with substantial effort, to closely match what is done here with Autotools, including testing and packaging.
This is NOT a plug for switching to CMake. Just adding color to the discussion.
from libmesh.
Well, I would hope it's still Turing-complete. ;-) And I'm not entirely opposed to switching to something, I just dream of something better than "with substantial effort" for "closely match". I probably need to keep an eye on both recently-developed and long-developed build systems, since it's not unimaginable that one of the latter will fix its problems before one of the former gets good. Either way, I'm too lazy to switch for anything short of "fixed" or "good"; hot garbage, just not worse than autotools anymore, wouldn't be worth the time.
The most interesting very-recent development I've seen was https://gitlab.com/esr/autodafe/-/blob/master/de-autoconfiscation.adoc - a new ESR project designed to turn autotools setups into plain (albeit gmake-specific) Makefiles, but not in the write-only way that autotools itself does. POSIX-environments-only, but WSL is less rickety than Cygwin so that's not the end of the world.
from libmesh.
Related Issues (20)
- Spurious -I/usr/include/tirpc is added when autodetecting libtirpc in linker path
- Refactor HDG NS example to use FEMContext
- VTK output then read loses block id information HOT 5
- MatSetValues_MPIAIJ() triggers malloc error at line 565 during libMesh termination HOT 6
- Installation error due to petsc compatibility HOT 12
- constrain_element_matrix changes the col_dofs vector size HOT 3
- Investigating the possibility of only having one solution vector in systems HOT 3
- Make Abaqus node/side ID maps available
- DM type 'libmesh' did not attach the DM to the matrix HOT 6
- Issues with latest libmesh devel -> master merge HOT 1
- Operator `()` of a petsc vector is not safe if used together with `set()` in a threaded loop.
- The 'mesh.read()' operation encounters errors when executed with 2048 processors HOT 1
- ExodusII IO has variable ID bug which can prevent coordinates from being read-in from a file HOT 4
- The release v1.7.2 doesn't have the tarballs attached HOT 1
- "No rule to make target..." installation error on Windows HOT 3
- Install FParser `fptypes.hh` header
- Libmesh out-of-date on spack HOT 3
- System destructor requires the mesh to still be around, through the dof map HOT 11
- Setting a variable to zero in a given iteration
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from libmesh.