This project is mirrored from https://github.com/riscv/riscv-gnu-toolchain.git. Pull mirroring failed .
Last successful update .
  1. 08 Aug, 2022 2 commits
  2. 09 Jun, 2022 1 commit
  3. 03 Jun, 2022 2 commits
  4. 02 Jun, 2022 1 commit
  5. 23 May, 2022 1 commit
  6. 14 May, 2022 1 commit
  7. 12 May, 2022 3 commits
  8. 22 Apr, 2022 1 commit
  9. 21 Apr, 2022 4 commits
  10. 20 Apr, 2022 1 commit
  11. 12 Apr, 2022 1 commit
  12. 11 Apr, 2022 2 commits
  13. 24 Mar, 2022 2 commits
  14. 08 Mar, 2022 1 commit
  15. 01 Mar, 2022 1 commit
  16. 24 Feb, 2022 6 commits
  17. 23 Feb, 2022 1 commit
  18. 11 Feb, 2022 3 commits
  19. 16 Jan, 2022 1 commit
  20. 15 Jan, 2022 1 commit
  21. 22 Dec, 2021 1 commit
  22. 21 Dec, 2021 1 commit
    • Palmer Dabbelt's avatar
      Set CXX to a nonexistent compiler when building glibc · 4ce4d457
      Palmer Dabbelt authored
      We set CXX=riscv64-unknown-linux-gnu-g++ (or something like that) when
      building glibc, but don't actually build a C++ compiler during stage 1.
      Under normal conditions this shouldn't cause any issues: that's either a
      working compiler (from PATH) or doesn't exist, in which case glibc's
      build scripts do the right thing and turn off C++.  Unfortunately I'm in
      the pathological situation of having a slightly-incompatible g++ in
      PATH, which glibc then attempts to use only to throw an error when
      linking (glibc isn't testing that much of the C++ toolchain, see
      <https://sourceware.org/bugzilla/show_bug.cgi?id=24183
      
      >).
      
      This simply sets CXX to something that's unlikely to exist during the
      glibc build, so the build scripts don't get confused.  I tried setting
      this to false, but everything was italic.
      
      Signed-off-by: default avatarPalmer Dabbelt <palmer@rivosinc.com>
      4ce4d457
  23. 19 Nov, 2021 1 commit
  24. 21 Sep, 2021 1 commit