Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

repro_build_env_declared and repro_deps_pinned overlook native C/C++ build systems and toolchains

Abierto
  • ¿Algo no está bien?
#433 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c, cpp, python
Área
devtools

Línea de trabajo

Start by locating the implementations of repro_build_env_declared and repro_deps_pinned, then read the referenced evaluation report for context. Check how they detect project files and produce verification guidance. Done means native build declarations and dependency manifests are considered for C/C++ projects, with relevant toolchain and ABI guidance.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

module-reproducibility

Description

For projects containing C or C++ source code, repro_build_env_declared and repro_deps_pinned only look for container/script files and high-level package locks (npm, Python, Cargo). They completely ignore native build declarations (Makefile, CMakeLists.txt, CMakePresets.json) and native dependency manifests (Conan, vcpkg).

What We Did

  1. Audited a repository containing C code built via Makefile with toolchain variables (CC = gcc-13).
  2. Ran darnit audit . --framework reproducibility --show-all.

What It Was Supposed To Do

When C/C++ files are present, the tool should check for C/C++ toolchain declarations and native dependency manifests, or tailor the verification guidance towards compiler version pinning and shared library ABI stability.

What We Got

Both controls returned INCONCLUSIVE (WARN), directing the user only to check for Dockerfiles, Nix files, or language lockfiles like Cargo.lock or uv.lock.

Proposed Enhancement

  1. When native code (.c, .cpp, .h) is detected in project context:
    • Check for CMake toolchain presets (CMakePresets.json) or compiler definitions in Makefiles.
    • Check for C/C++ dependency managers (conan.lock, vcpkg.json).
  2. Provide verification steps relevant to native code (pinning system toolchain and libc versions).

Reference report: https://github.com/Jaydeep869/darnit/blob/reproducibility-evaluation/reports/experiment_2_c_ctypes.md#bug-report-5-repro_build_env_declared-ignores-makefiles-toolchain-files-and-native-cc-compiler-definitions

Lenguaje dominante
Python
Estrellas
22
Forks
27
Merge medio
1 d 20 h
PR fusionados (30 d)
39

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de darnitdevorg/darnit

Todos los issues de darnitdevorg/darnit

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.