Marfs must be built with a valid configuration but uses a different one at run time.

[cadejager]

Marfs must be build with a valid configuration. However, this configuration is not used at run time as it uses the one set in $MARFSCONFIGRC. Is it possible to remove the need for a configfile at buildtime for marfs?

[jti-lanl]

It would be easy to remove this -- it looks like it's just a step in the libconfig makefile that serves to validate the config, which might be useful because the runtime reporting of configuration-parse problems (in some cases) is terrible. By default, the local build of libconfig just uses marfs_cctest.cfg, which is a "generic" configuration. However, it looks like build_marfs overrides this with $MARFSCONFIG, for the libconfig build. If you don't have MARFSCONFIG set (e.g. a generic build), this will break the libconfig build.

In an effort to keep the build-time parse-test, I tweaked the build_marfs to allow libconfig to fall-back to using marfs_cctest.cfg, if MARFSCONFIG is not defined. Does that resolve the issue, or would you truly rather just suppress the parse-test phase?