1. 16 Jan, 2019 1 commit
  2. 08 Jan, 2019 3 commits
  3. 07 Jan, 2019 3 commits
  4. 21 Dec, 2018 1 commit
    • Nick Mathewson's avatar
      Try @warning_flags to avoid bloating verbose make logs · 97c9ced7
      Nick Mathewson authored
      We now accumulate warning flags in a separate variable,
      "TOR_WARNING_FLAGS", and write it to a "warning_flags" file.  Then
      we test whether the compiler will accept "@warning_flags": if so, we
      put "@warning_flags" in the CFLAGS; if not, we copy the contents of
      "$TOR_WARNING_FLAGS" into the CFLAGS.
      
      Closes ticket 28924.
      97c9ced7
  5. 18 Dec, 2018 2 commits
  6. 16 Nov, 2018 2 commits
  7. 09 Nov, 2018 1 commit
  8. 08 Nov, 2018 1 commit
  9. 07 Nov, 2018 1 commit
  10. 02 Nov, 2018 2 commits
  11. 29 Oct, 2018 1 commit
  12. 17 Oct, 2018 2 commits
  13. 02 Oct, 2018 1 commit
    • Alex Crichton's avatar
      Remove the `link_rust.sh.in` script · 6ebb2c46
      Alex Crichton authored
      This is no longer necessary with upstream rust-lang/rust changes as well
      as some local tweaks. Namely:
      
      * The `-fsanitize=address`-style options are now passed via `-C
        link-args` through `RUSTFLAGS`. This obviates the need for the shell
        script.
      * The `-C default-linker-libraries`, disabling `-nodefaultlibs`, is
        passed through `RUSTFLAGS`, which is necessary to ensure that
        `-fsanitize=address` links correctly.
      * The `-C linker` option is passed to ensure we're using the same C
        compiler as normal C code, although it has a bit of hackery to only
        get the `gcc` out of `gcc -std=c99`
      6ebb2c46
  14. 21 Sep, 2018 1 commit
  15. 20 Sep, 2018 1 commit
  16. 18 Sep, 2018 1 commit
  17. 17 Sep, 2018 1 commit
  18. 13 Sep, 2018 1 commit
  19. 12 Sep, 2018 1 commit
  20. 10 Sep, 2018 4 commits
  21. 07 Sep, 2018 5 commits
  22. 04 Sep, 2018 1 commit
  23. 28 Aug, 2018 1 commit
  24. 24 Aug, 2018 2 commits