OS Specific Toolchain: Difference between revisions

Jump to navigation Jump to search
[unchecked revision][unchecked revision]
Content deleted Content added
Update OS Specific Toolchain article to latest binutils and gcc and clean up article
#ifdef BFD64 →‎bfd/config.bfd
Line 43: Line 43:
targ64_selvecs=bfd_elf64_x86_64_vec
targ64_selvecs=bfd_elf64_x86_64_vec
;;
;;
#ifdef BFD64
x86_64-*-myos*)
x86_64-*-myos*)
targ_defvec=bfd_elf64_x86_64_vec
targ_defvec=bfd_elf64_x86_64_vec
Line 48: Line 49:
want64=true
want64=true
;;
;;
#endif
</source>
</source>


Be sure to follow the instructions in the comment block above the list and add your entry beneath the comment "<tt>#START OF targmatch.h</tt>". If you like, you could support different object formats (look at other entries in the list, and the contents of 'bfd' for hints) and also provide more than one to the <tt>targ_selvecs</tt> line. For instance, you can support coff object files if you add <tt>i386coff_vec</tt> to the <tt>targ_selvecs</tt> list.
Be sure to follow the instructions in the comment block above the list and add your entry beneath the comment "<tt>#START OF targmatch.h</tt>". If you like, you could support different object formats (look at other entries in the list, and the contents of 'bfd' for hints) and also provide more than one to the <tt>targ_selvecs</tt> line. For instance, you can support coff object files if you add <tt>i386coff_vec</tt> to the <tt>targ_selvecs</tt> list. For some reason, all the <tt>x86_64</tt> entries in the file file are wrapped in <tt>#ifdef BFD64</tt>, it's probably prudent to do it yourself as well.


=== gas/configure.tgt ===
=== gas/configure.tgt ===