Mark Grondona

Also from #2040: > I kind of wonder if SCR support will be a function of the "job shell" (the user process that actually runs user compute tasks). Resources aren't...

Yes, the extended help is provided by an installed JSON file, which allows other Flux subprojects to optionally include their commands in `flux help` output. Since `sysconfdir` can be separately...

I think I'm still confused, that has nothing to do with the `help.d` directory. Everything should be relative to `/prefix` with any autotools project, so I'm not sure exactly what...

BTW, if you compile with `--without-python` many things will not work, including `flux start` which will try to run at least a couple python scripts during startup via rc scripts.

> Right the cross compilation environment I am using compiles in a jail, and then I want to distribute the produced binaries and libraries. Compilation in a jail + distribution...

Thanks, so we just have to figure out why flux-core doesn't "just work" since I didn't see anything tricky going on there. I'll try to help more tomorrow.

Yes, your prefix was set to /workspace/destdir, but flux isn't installed there. You can get it to work by setting FLUX_RC_PATH, but like I said it will fail soon after...

Ah, yeah, sorry I wasn't thinking clearly last night. The `rc1` `rc3` paths can be set as a broker attributes, e.g. to disable them completely: ``` $ flux start -o,-Sbroker.rc1_path=,-Sbroker.rc3_path=...

BTW, what is the use case for using and starting Flux in this manner? Is it only to run automated tests of the Julia bindings in the build system, or...

> Testing is one use-case, but for CESMIX I want to try and provide a Julia driver that talks to Flux and if necessary creates its own Flux instance to...