1. 02 Jun, 2017 1 commit
  2. 01 Jun, 2017 3 commits
  3. 09 May, 2017 2 commits
  4. 05 May, 2017 1 commit
  5. 26 Apr, 2017 2 commits
  6. 25 Apr, 2017 1 commit
  7. 05 Dec, 2016 1 commit
  8. 01 Dec, 2016 2 commits
  9. 13 Oct, 2016 1 commit
  10. 11 Oct, 2016 1 commit
  11. 10 Oct, 2016 1 commit
  12. 07 Oct, 2016 1 commit
  13. 06 Oct, 2016 11 commits
    • Hendryk Bockelmann's avatar
    • Hendryk Bockelmann's avatar
    • Hendryk Bockelmann's avatar
    • Nicolai Stange's avatar
      cleanup: autotools: remove superfluous uninstall-local target · ff5fbe12
      Nicolai Stange authored and Hendryk Bockelmann's avatar Hendryk Bockelmann committed
      Automake is capable of handling the uninstallations of files it knows about
      by itself and thus, the uninstall-local target in src/Makefile is
      superfluous. Remove it.
      ff5fbe12
    • Nicolai Stange's avatar
      cleanup: autotools: replace clean-local target by CLEANFILES mechanism · c644112b
      Nicolai Stange authored and Hendryk Bockelmann's avatar Hendryk Bockelmann committed
      CLEANFILES is way easier than writing custom clean-local hooks. Employ it.
      c644112b
    • Nicolai Stange's avatar
      autotools: add sct.h to BUILT_SOURCES · 5a0dcfc5
      Nicolai Stange authored and Hendryk Bockelmann's avatar Hendryk Bockelmann committed
      sct.h is generated at build time. Add it to BUILT_SOURCES to ensure that
      it gets built before anything else unconditionally.
      5a0dcfc5
    • Nicolai Stange's avatar
      cleanup: autotools: exclude sct.h from 'make dist' · ba53a33b
      Nicolai Stange authored and Hendryk Bockelmann's avatar Hendryk Bockelmann committed
      The sct.h header is generated at build time and depends on the
      configuration. Do not include it in 'make dist' by putting it into
      the nodist_pkginclude_HEADERS variable.
      
      Furthermore, remove the *_SOURCES dependencies on sct.h from the programs
      in tests/ -- the Automake manual explicitly says that this doesn't work
      (section 9.4.1 Built Sources Example) and they cause sct.h to be included
      in the 'make dist' tarball.
      ba53a33b
    • Nicolai Stange's avatar
      feature: autotools: allow for VPATH builds · 2de11d4a
      Nicolai Stange authored and Hendryk Bockelmann's avatar Hendryk Bockelmann committed
      Currently, the way src/sct.h is generated forbids out-of-tree builds.
      
      Fix this by giving the util/gen_public_header.pl script full paths
      to the source headers, i.e. prefix them by $(srcdir).
      
      For the tests directory, add -I $(top_builddir)/src to its CPPFLAGS in
      order to make the tests compilations find the sct.h places in the build
      directory now.
      2de11d4a
    • Nicolai Stange's avatar
      cleanup: autotools: don't modify user chosen installation prefix · 35cdbf9b
      Nicolai Stange authored and Hendryk Bockelmann's avatar Hendryk Bockelmann committed
      Currently, configure constructs a $SETUPTYPE string based on the selected
      configuration and appends that to installation prefix as given by --prefix.
      
      This behaviour is not only unusual, but limits the user to completely
      determine the final installation path.
      
      Abandon it. Namely,
      - purge the --with-mpitype option from configure,
      - do not construct a $SETUPTYPE string,
      - purge any reference to $SETUPTYPE from the Makefile.am's.
      
      Additionally, in order to avoid name clashs in the case of
      --enable-fakelib, install the "real" sct headers into $pkgincludedir, e.g.
      $prefix/include/sct, and the fake ones into a directory named "nosct"
      thereunder. Rename the fake libsct.la to libnosct.la.
      
      The above changes render the install-all make target, which reconfigures
      and rebuilds in all combinations of w/ and w/o OpenMP and MPI,
      disfunctional. Functionality of that kind is better preserved in some
      user defined wrapper scripts around the build process anyway and thus,
      purge the install-all make target.
      
      Finally, adapt the pkgconfig/sct.pc.in to properly reflect the changes.
      35cdbf9b
    • Nicolai Stange's avatar
      git repo: add subdir specific build generated files to .gitgnore · ee539386
      Nicolai Stange authored and Hendryk Bockelmann's avatar Hendryk Bockelmann committed
      While the common build generated files are excluded by the toplevel
      .gitignore, the ones specific to the individual subdirectories are not.
      
      Create a .gitignore per Makefile.am and include every build generated file
      specific to that Makefile.am.
      ee539386
    • Nicolai Stange's avatar
      cleanup: git repo: don't track autogenerated autotools files · eacd15bc
      Nicolai Stange authored and Hendryk Bockelmann's avatar Hendryk Bockelmann committed
      The current state of the upstream git repo is that most files created
      by autoreconf are tracked, but not all: the Makefile.in's are missing
      since commit d5c14d99 ("cleanup git repo for autotools usage").
      Thus, the build system as distributed by the repo isn't in a workable
      state.
      
      It is common practice to not track autogenerated files in VCS and so,
      instead of adding the missing Makefile.in's to the repo, purge everything
      else recoverable by a simple run of autoreconf.
      
      Namely,
      - git rm everything stemming from autoreconf,
      - add everything generated by autoreconf to .gitignore,
      - remove the check for the autotools' version from autgen.sh -- version
        requirements are set in configure.ac already.
      
      In addition, add some files created by the configure and build process to
      .gitignore
      
      Fixes: d5c14d99 ("cleanup git repo for autotools usage")
      eacd15bc
  14. 04 Aug, 2016 2 commits
  15. 29 Jun, 2016 8 commits
    • Nicolai Stange's avatar
      cleanup: autotools: remove superfluous uninstall-local target · 13994744
      Nicolai Stange authored
      Automake is capable of handling the uninstallations of files it knows about
      by itself and thus, the uninstall-local target in src/Makefile is
      superfluous. Remove it.
      13994744
    • Nicolai Stange's avatar
      cleanup: autotools: replace clean-local target by CLEANFILES mechanism · 8e09aa6b
      Nicolai Stange authored
      CLEANFILES is way easier than writing custom clean-local hooks. Employ it.
      8e09aa6b
    • Nicolai Stange's avatar
      autotools: add sct.h to BUILT_SOURCES · 9756ddea
      Nicolai Stange authored
      sct.h is generated at build time. Add it to BUILT_SOURCES to ensure that
      it gets built before anything else unconditionally.
      9756ddea
    • Nicolai Stange's avatar
      cleanup: autotools: exclude sct.h from 'make dist' · 1310133f
      Nicolai Stange authored
      The sct.h header is generated at build time and depends on the
      configuration. Do not include it in 'make dist' by putting it into
      the nodist_pkginclude_HEADERS variable.
      
      Furthermore, remove the *_SOURCES dependencies on sct.h from the programs
      in tests/ -- the Automake manual explicitly says that this doesn't work
      (section 9.4.1 Built Sources Example) and they cause sct.h to be included
      in the 'make dist' tarball.
      1310133f
    • Nicolai Stange's avatar
      feature: autotools: allow for VPATH builds · a059de5f
      Nicolai Stange authored
      Currently, the way src/sct.h is generated forbids out-of-tree builds.
      
      Fix this by giving the util/gen_public_header.pl script full paths
      to the source headers, i.e. prefix them by $(srcdir).
      
      For the tests directory, add -I $(top_builddir)/src to its CPPFLAGS in
      order to make the tests compilations find the sct.h places in the build
      directory now.
      a059de5f
    • Nicolai Stange's avatar
      cleanup: autotools: don't modify user chosen installation prefix · 2e74165a
      Nicolai Stange authored
      Currently, configure constructs a $SETUPTYPE string based on the selected
      configuration and appends that to installation prefix as given by --prefix.
      
      This behaviour is not only unusual, but limits the user to completely
      determine the final installation path.
      
      Abandon it. Namely,
      - purge the --with-mpitype option from configure,
      - do not construct a $SETUPTYPE string,
      - purge any reference to $SETUPTYPE from the Makefile.am's.
      
      Additionally, in order to avoid name clashs in the case of
      --enable-fakelib, install the "real" sct headers into $pkgincludedir, e.g.
      $prefix/include/sct, and the fake ones into a directory named "nosct"
      thereunder. Rename the fake libsct.la to libnosct.la.
      
      The above changes render the install-all make target, which reconfigures
      and rebuilds in all combinations of w/ and w/o OpenMP and MPI,
      disfunctional. Functionality of that kind is better preserved in some
      user defined wrapper scripts around the build process anyway and thus,
      purge the install-all make target.
      
      Finally, adapt the pkgconfig/sct.pc.in to properly reflect the changes.
      2e74165a
    • Nicolai Stange's avatar
      git repo: add subdir specific build generated files to .gitgnore · 77330f4d
      Nicolai Stange authored
      While the common build generated files are excluded by the toplevel
      .gitignore, the ones specific to the individual subdirectories are not.
      
      Create a .gitignore per Makefile.am and include every build generated file
      specific to that Makefile.am.
      77330f4d
    • Nicolai Stange's avatar
      cleanup: git repo: don't track autogenerated autotools files · dcd65071
      Nicolai Stange authored
      The current state of the upstream git repo is that most files created
      by autoreconf are tracked, but not all: the Makefile.in's are missing
      since commit d5c14d99 ("cleanup git repo for autotools usage").
      Thus, the build system as distributed by the repo isn't in a workable
      state.
      
      It is common practice to not track autogenerated files in VCS and so,
      instead of adding the missing Makefile.in's to the repo, purge everything
      else recoverable by a simple run of autoreconf.
      
      Namely,
      - git rm everything stemming from autoreconf,
      - add everything generated by autoreconf to .gitignore,
      - remove the check for the autotools' version from autgen.sh -- version
        requirements are set in configure.ac already.
      
      In addition, add some files created by the configure and build process to
      .gitignore
      
      Fixes: d5c14d99 ("cleanup git repo for autotools usage")
      dcd65071
  16. 28 Jun, 2016 2 commits
    • Nicolai Stange's avatar
      bug fix: nested timers: search harder for common ancestors · baed2cd7
      Nicolai Stange authored
      Consider the two timer nestings
      
        a => b => c
      
      and
      
        a => c
      
      In case they're encounted in the order presented, the ->active_under
      of c will be set to -1 (root), because update_timer_stack_atstart()
      only checks whether the current ->active_under is on the callstack.
      After the first nesting has been processed, c->active_under == b and b is
      not on the callstack of a => c.
      
      The outcome is different if the two nestings are processed in reversed
      order, i.e. a => c first, followed by a => b => c: the final
      c->active_under will be a in this case.
      
      Fix this by not only checking whether the current element's ->active_under
      is on the callstack, but if any of its common ancestors, i.e. any member
      of the whole list linked by ->active_under can be found.
      
      In fact, do not check the whole callstack, but take advantage of its
      invariants and traverse only the list linked by ->active_under rooted at
      its topmost element.
      baed2cd7
    • Nicolai Stange's avatar
      update_timer_stack_atstart(): pass whole stats array · 0ea12999
      Nicolai Stange authored
      Since the sct_stats_type instances' chains of common ancestors are linked
      via ->active_under through their timer indicies,
      update_timer_stack_atstart() will not only need access to the current
      sct_stats_type instance, but to all of them in order to be able to walk
      those chains upwards.
      
      Instead of only passing the current sct_stats_type instance to
      update_timer_stack_atstart(), give it a pointer to the array containing all
      of them.
      0ea12999