Skip to content

fix: make elf32 and elf64 features additive (fixes #348)#535

Open
leno23 wants to merge 1 commit into
m4b:masterfrom
leno23:fix/elf32-elf64-additive-features-348
Open

fix: make elf32 and elf64 features additive (fixes #348)#535
leno23 wants to merge 1 commit into
m4b:masterfrom
leno23:fix/elf32-elf64-additive-features-348

Conversation

@leno23

@leno23 leno23 commented May 25, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Make elf32 and elf64 Cargo features mutually enable each other so selecting only one no longer breaks the build.

Fixes #348.

The ELF parser currently references both 32-bit and 64-bit modules in shared code paths. Requiring both features when either is enabled matches Cargo's additive feature guidance and avoids compile failures for users trimming dependencies.

Suggested approach from @d-e-s-o in the issue.

Test plan

  • cargo check --no-default-features --features "std,elf32"
  • cargo check --no-default-features --features "std,elf64"
  • cargo test --lib

Enable each ELF feature to pull in the other so builds with only
elf32 or elf64 no longer fail (fixes m4b#348).

Co-authored-by: Cursor <cursoragent@cursor.com>
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.

features = ["std", "elf32"] doesn't build

1 participant