Skip to content

Include stdint.h in Utilities/Memory.h - #90

Merged
attermann merged 1 commit into
attermann:masterfrom
jmpuch:memory-stdint
Nov 9, 2026
Merged

attermann merged 1 commit into
attermann:masterfrom
jmpuch:memory-stdint

Conversation

@jmpuch

@jmpuch jmpuch commented Sep 26, 2026

Copy link
Copy Markdown
Contributor

Problem

src/microReticulum/Utilities/Memory.h uses uint8_t, uint32_t and uint64_t without including <stdint.h>. With GCC 15 (Ubuntu 26.04, pio test -e native-local), every native build that pulls in this header fails:

src/microReticulum/Utilities/Memory.h:37:25: error: 'uint8_t' does not name a type

Older toolchains happened to get the typedefs through another header.

Change

Add #include <stdint.h> to Memory.h. No functional change.

Testing

  • Native (Linux, GCC 15.2): pio test -e native-local for test_crypto, test_transport, test_rns_loopback, test_bytes, test_general now build and pass.
  • ESP32 (ttgo-lora32-v21) and nRF52 builds are unaffected (the include is a no-op where the types were already visible).

🤖 Generated with Claude Code

Memory.h uses uint8_t/uint32_t/uint64_t without including <stdint.h>;
native builds with GCC 15 fail with "'uint8_t' does not name a type".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@attermann

Copy link
Copy Markdown
Owner

Thanks for tracking this down and for including the exact GCC 15 error. Adding <stdint.h> to Memory.h is the right fix and it's a safe change on every platform.

The CI run on this PR didn't start (0 jobs), so I'll re-trigger it. If it comes back green on the native and embedded builds, it looks good to me.

@attermann
attermann merged commit f081b88 into attermann:master Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants