Make often fails unless "make clean" is run first. #4118

issue rebroad opened this issue on May 2, 2014
  1. rebroad commented at 7:57 AM on May 2, 2014: contributor

    I am seeing a lot of issues being raised due to compilation errors where the "solution" quite often is to run "make clean" first. This is not ideal as it takes significant time and energy to recompile everything.

  2. laanwj commented at 8:02 AM on May 2, 2014: member

    It's not ideal, but it is extremely common in software development. If you change a .cpp or .h file the dependencies should be picked up automatically. however if the build system itself is changed (Makefile.am, configure.ac, ...), it is frequently infeasible to detect the dependencies that need to be recompiled. And for example if some compiler flag was added, everything has to be recompiled either way.

  3. laanwj added the label Build system on May 2, 2014
  4. veox commented at 12:17 PM on May 9, 2014: none

    @rebroad, are you using ccache?

  5. theuni commented at 3:54 PM on June 6, 2014: member

    Non-recursive make is in, this can be closed. Any case where a 'make clean' is now needed would be an individual bug.

  6. laanwj closed this on Jun 6, 2014

  7. MarcoFalke locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-17 18:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me