# Version v1.11.7 fails to build from source

**URL:** https://discourse.julialang.org/t/version-v1-11-7-fails-to-build-from-source/132443
**Category:** General Usage
**Created:** [September 16, 2025, 3:03pm UTC](https://discourse.julialang.org/t/version-v1-11-7-fails-to-build-from-source/132443 "2025-09-16T15:03:14Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Dylan\_Thurston](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dylan_thurston/32/218658_2.png) [@Dylan\_Thurston](https://discourse.julialang.org/u/Dylan_Thurston)
#### Post date: [September 16, 2025, 3:03pm UTC](https://discourse.julialang.org/t/version-v1-11-7-fails-to-build-from-source/132443/1 "2025-09-16T15:03:14Z")

</div>

I tried to update to the latest v1.11.7, and it fails to build from source (on my Debian GNU/Linux system). I get a lot of error messages, starting with complaints about `SIZE_MAX` being undefined when compiling `src/debuginfo.o`. I can’t upload the complete log here (no permissions), but the beginning is below.

Version 1.11.6 compiled fine on this same computer.

I’m surprised not to see anyone else encountering this. What changed? Id like to sort out what’s happening a little more and file a github issue.

```julia-auto
    CC src/debuginfo.o
In file included from /usr/local/src/julia-1.11/usr/include/llvm/DebugInfo/DIContext.h:17,
                 from /usr/local/src/julia-1.11/src/debuginfo.cpp:6:
/usr/local/src/julia-1.11/usr/include/llvm/ADT/SmallVector.h:1317:5: warning: 'SIZE_MAX' is not defined, evaluates to '0' [-Wundef]
 1317 | #if SIZE_MAX > UINT32_MAX
      | ^ ~~~~~~~
/usr/local/src/julia-1.11/usr/include/llvm/ADT/SmallVector.h:1317:16: warning: 'UINT32_MAX' is not defined, evaluates to '0' [-Wundef]
 1317 | #if SIZE_MAX > UINT32_MAX
      | ^ ~~~~~~~~~
/usr/local/src/julia-1.11/usr/include/llvm/ADT/SmallVector.h:109:62: error: 'uint64_t' was not declared in this scope
  109 | std::conditional_t<sizeof(T) < 4 && sizeof(void *) >= 8, uint64_t,
      | ^ ~~~~~~~
/usr/local/src/julia-1.11/usr/include/llvm/ADT/SmallVector.h:29:1: note: 'uint64_t' is defined in header '<cstdint>'; this is probably fixable by adding '#include <cstdint>'
   28 | #include <memory>
  +++ |+#include <cstdint>
   29 | #include <new>

```

---

<div class="post-metadata">

### Author: ![dilumaluthge](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dilumaluthge/32/29283_2.png) [@dilumaluthge](https://discourse.julialang.org/u/dilumaluthge)
#### Post date: [September 16, 2025, 3:19pm UTC](https://discourse.julialang.org/t/version-v1-11-7-fails-to-build-from-source/132443/2 "2025-09-16T15:19:07Z")

</div>

Any chance you could bisect (on the `release-1.11` branch)?

---

<div class="post-metadata">

### Author: ![Dylan\_Thurston](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dylan_thurston/32/218658_2.png) [@Dylan\_Thurston](https://discourse.julialang.org/u/Dylan_Thurston)
#### Post date: [September 16, 2025, 3:28pm UTC](https://discourse.julialang.org/t/version-v1-11-7-fails-to-build-from-source/132443/4 "2025-09-16T15:28:53Z")

</div>

An update: I should have tried this first, but v1.11.6 also failed to build. So it’s some other package on my computer that changed since I previously built Julia (sometime in August). I will investigate!

---

<div class="post-metadata">

### Author: ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)
#### Post date: [September 16, 2025, 3:32pm UTC](https://discourse.julialang.org/t/version-v1-11-7-fails-to-build-from-source/132443/5 "2025-09-16T15:32:22Z")

</div>

> [@Dylan\_Thurston](#):
>
> on my Debian GNU/Linux system

Can you provide more information about the version of the system?

---

<div class="post-metadata">

### Author: ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)
#### Post date: [September 16, 2025, 3:38pm UTC](https://discourse.julialang.org/t/version-v1-11-7-fails-to-build-from-source/132443/6 "2025-09-16T15:38:26Z")

</div>

> [@Dylan\_Thurston](#):
>
> ```julia-auto
> usr/local/src/julia-1.11/usr/include/llvm/ADT/SmallVector.h:109:62: error: 'uint64_t' was not declared in this scope
> 109 | std::conditional_t<sizeof(T) < 4 && sizeof(void *) >= 8, uint64_t,
> | ^ ~~~~~~~
> /usr/local/src/julia-1.11/usr/include/llvm/ADT/SmallVector.h:29:1: note: 'uint64_t' is defined in header '<cstdint>'; this is probably fixable by adding '#include <cstdint>'
> 28 | #include <memory>
> +++ |+#include <cstdint>
> 29 | #include <new>
> 
> ```

Are you using GCC 15? I think you’re running into an upstream LLVM issue:

> <https://github.com/JuliaLang/julia/issues/58478#issuecomment-3161411290>
>
> Just tried to compile Julia on my local dev machine (yay rolling release).
> 
> Fail…s with errors like: \`llvm/ADT/SmallVector.h:109:62: error: 'uint64\_t' was not declared in this scope\`
> Similar to https://github.com/root-project/root/issues/17444
> 
> We likely need the patches from https://github.com/root-project/root/pull/17510
> 
> Caused by https://gcc.gnu.org/pipermail/gcc-patches/2024-August/659176.html
> 
> 
> For anyone else who runs into this an is looking for a quick solution:
> 
> \`\`\`
> ~/s/julia-1.11 (release-1.11)\> cat Make.user
> override CC=gcc-14
> override CXX=g++-14
> \`\`\`
> 
> With the \`gcc-14\` package installed.

---

<div class="post-metadata">

### Author: ![Dylan\_Thurston](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dylan_thurston/32/218658_2.png) [@Dylan\_Thurston](https://discourse.julialang.org/u/Dylan_Thurston)
#### Post date: [September 16, 2025, 3:43pm UTC](https://discourse.julialang.org/t/version-v1-11-7-fails-to-build-from-source/132443/7 "2025-09-16T15:43:18Z")

</div>

Indeed I am, and the workaround suggested in that issue (add the flag `CXXFLAGS="-include cstdint"` to make) seems to fix the problem. Thanks so much!