Package builds on ci but not my machine

Help
1

Hi,

I’m trying to finalize this PR by running: nix run nixpkgs#nixpkgs-review – pr 475883

The problem is that it fails to build on my computer but it seems to build just fine in CI.

Should I be worried that it fails to build on my computer, but builds just fine in CI?
The only way I could test on my computer while developing was to target the 25.11 branch and that was fine. It would fail against unstable and master.

Any help would be appreciated.
The exact error is a c++ compilation error:

```

ERROR: /build/output/external/com_google_absl/absl/flags/BUILD.bazel:175:11: Compiling absl/flags/reflection.cc failed: (Exit 1): gcc failed: error executing CppCompile command (from target @@com_google_absl//absl/flags:reflection) /nix/store/r9wbjib6xxjkyb9yvjvrkl4sq61i2lyn-gcc-wrapper-15.2.0/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ‘-std=c++14’ … (remaining 35 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
In file included from /nix/store/qarrb8yfby1yyypm32vabzgxgq3w41ma-gcc-15.2.0/include/c++/15.2.0/cassert:46,
from external/com_google_absl/absl/container/internal/container_memory.h:18,
from external/com_google_absl/absl/container/flat_hash_map.h:40,
from external/com_google_absl/absl/flags/reflection.h:29,
from external/com_google_absl/absl/flags/reflection.cc:16:
external/com_google_absl/absl/container/internal/container_memory.h: In function ‘void* absl::lts_20240116::container_internal::Allocate(Alloc*, size_t)’:
external/com_google_absl/absl/container/internal/container_memory.h:66:27: error: ‘uintptr_t’ does not name a type [-Wtemplate-body]
66 | assert(reinterpret_cast<uintptr_t>(p) % Alignment == 0 &&
| ^~~~~~~~~
external/com_google_absl/absl/container/internal/container_memory.h:31:1: note: ‘uintptr_t’ is defined in header ‘’; this is probably fixable by adding ‘#include ’
30 | #include “absl/utility/utility.h”
+++ |+#include
31 |
Target //generator:protoc-gen-js failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 18.347s, Critical Path: 10.07s
INFO: 933 processes: 542 internal, 391 linux-sandbox.
ERROR: Build did NOT complete successfully
```

2

The build error is not from your PR itself but a downstream issue of protoc-gen-js being broken after Some packages may fail to compile with GCC 15 · Issue #475479 · NixOS/nixpkgs · GitHub . The relevant subissue calls out anytype specifically as a reproducer.

I’m not too sure which CI you are referring to but at lest GitHub CI does not appear to have tried to build the package.

3

Thanks! I missed that it didn’t build.

I assumed wrongly that the build step was to actually build the package.