Page MenuHomeFreeBSD

crunchide: always include both 32- and 64-bit ELF for cross builds
ClosedPublic

Authored by emaste on Apr 17 2015, 3:47 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, May 1, 2:46 PM
Unknown Object (File)
Sat, Apr 26, 7:17 PM
Unknown Object (File)
Fri, Apr 25, 2:26 AM
Unknown Object (File)
Sun, Apr 20, 5:52 PM
Unknown Object (File)
Mon, Apr 14, 6:12 AM
Unknown Object (File)
Mon, Apr 14, 5:55 AM
Unknown Object (File)
Mon, Apr 14, 3:12 AM
Unknown Object (File)
Mar 12 2025, 11:07 AM
Subscribers
None

Details

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

emaste retitled this revision from to crunchide: always include both 32- and 64-bit ELF for cross builds.
emaste updated this object.
emaste edited the test plan for this revision. (Show Details)
emaste added reviewers: imp, rodrigc, jhb.
usr.sbin/crunch/crunchide/exec_elf32.c
181

While you are cleaning up, do we need all these ifndef for things that we define in the base?

usr.sbin/crunch/crunchide/exec_elf32.c
181

almost certainly not, but I'd rather do it as a subsequent commit

emaste added a reviewer: emaste.
This revision is now accepted and ready to land.Apr 18 2015, 12:17 AM

Another possible cleanup would be to rename elf_exec32.c to elf_exec.c and have elf_exec32.c look like elf_exec64.c where both of them just set ELFSIZE and include the common file (this is what we do in other places). That would be a follow up though.

In D2314#8, @jhb wrote:

Another possible cleanup would be to rename elf_exec32.c to elf_exec.c and have elf_exec32.c look like elf_exec64.c where both of them just set ELFSIZE and include the common file (this is what we do in other places). That would be a follow up though.

Yeah. I recently discovered that NetBSD has a number of crunch* improvements, so we might want to look at importing it as vendor source, or cherry-pick changes from there.