Building Einstein Toolkit requires using 'Build' twice

Create issue
Issue #1305 closed
srichers created an issue

When building a config in EinsteinToolkit for the first time the following errors come up: find: configs/Cfg1/ThornList': No such file or directory find:configs/Cfg1/config-data': No such file or directory find: `configs/Cfg1/config-info': No such file or directory

Checking the folder in .mojaveconfig/projectname after the build reveals the files are present. Running build a second time completes successfully. This does not happen when running simfactory directly, nor does it happen when using Mojave to build the WaveToy demo.

(note, optionfile allows building using 32 processes...just a timing issue?)


Comments (10)

  1. Erik Schnetter
    • removed comment

    I added an additional dependency to Formaline that may resolve this issue. Can you try again?

  2. srichers reporter
    • removed comment

    did "svn up" in arrangements/CactusUtils/Formaline which updated src/make.configuration.deps

    Unfortunately the problem still persists. I find it odd that it happens only when using Mojave, though.

  3. Erik Schnetter
    • removed comment

    Can you post a log file of all commands executed? Simfactory has a "--verbose" option, and Cactus has "make VERBOSE=yes".

  4. srichers reporter
    • removed comment

    More detailed description: (sorry for the spam)

    mojave.log - copy of output to console when clicking mojave->Build simfactory.log - copy of output when executing the command in the first line of mojave.log after changing to the directory in the second line of mojave.log

  5. Erik Schnetter
    • removed comment

    The find command fails very late, long after thorns have begun to be built. At that time, the ThornList obviously exists.

    Can you add a "pwd" statement before the find to see in which directory the find command executes?

  6. anonymous
    • removed comment

    Sorry I didn't notice this ticket. The fix is quite simple. Apparently I allowed the / character to appear in names at some point, which was probably a bad idea. The following small change allows the par file to work, and the ET test suite still passes.


    --- (revision 4991) +++ (working copy) @@ -722,7 +722,7 @@ "# Note that / occurs in some par files. It is my\n" "# feeling that this should require quote marks.\n"

    • "name = [@a-zA-Z_][@/a-zA-Z0-9_-]*\n"
    • "name = [@a-zA-Z_][@a-zA-Z0-9_-]\n" "dname = [0-9][a-zA-Z_]{2,}\n" "inquot = ({var}|\\.|[^\\\"])\n" "fname = \.?/[-\./0-9a-zA-Z_]+\n"
  7. Log in to comment