search for: bi386

...binary to an ELF object > file > ``` > objcopy -I binary -O elf64-x86-64 foo.bin foo.o > ``` > This is sometimes used for embedding binary files for use by drivers and > such. > Yea, unfortunately the command-line you actually end up needing is more like: objcopy -I binary -Bi386:x86-64 -Oelf64-x86-64 --rename-section .data=.rodata,alloc,load,readonly,data,contents --add-section .note.GNU-stack=/dev/null Having to manually invoke objcopy and know what to specify for the -B and -O options, and to know you need the .note.GNU-stack section, and how to move it into rodata...it...

...-O elf64-x86-64 foo.bin foo.o >>> ``` >>> This is sometimes used for embedding binary files for use by drivers and >>> such. >>> >> >> Yea, unfortunately the command-line you actually end up needing is more >> like: >> objcopy -I binary -Bi386:x86-64 -Oelf64-x86-64 --rename-section >> .data=.rodata,alloc,load,readonly,data,contents --add-section >> .note.GNU-stack=/dev/null >> >> Having to manually invoke objcopy and know what to specify for the -B and >> -O options, and to know you need the .note.GNU-stack...

LLVM already implements its own version of almost all of binutils. The exceptions to this rule are objcopy and strip. This is a proposal to implement an llvm version of objcopy/strip to complete llvm’s binutils. Several projects only use gnu binutils because of objcopy/strip. LLVM itself uses objcopy in fact. Chromium and Fuchsia currently use objcopy as well. If you want to distribute your build