Show simple item record

dc.contributor.authorChamberlain, Steve
dc.contributor.authorTaylor, Ian Lance
dc.contributor.authorChamberlain, Steveen_US
dc.contributor.authorTaylor, Ian Lanceen_US
dc.date.accessioned2016-06-14T06:39:22Z
dc.date.available2016-06-14T06:39:22Z
dc.date.issued2010en_US
dc.identifier.otherHPU4160127en_US
dc.identifier.urihttps://lib.hpu.edu.vn/handle/123456789/21416
dc.description.abstractLd combines a number of object and archive files, relocates their data and ties up symbol references. Usually the last step in compiling a program is to run ld. ld accepts Linker Command Language files written in a superset of AT&T’s Link Editor Command Language syntax, to provide explicit and total control over the linking process. This version of ld uses the general purpose BFD libraries to operate on object files. This allows ld to read, combine, and write object files in many different formats—for example, COFF or a.out. Different formats may be linked together to produce any available kind of object file. See Chapter 5 [BFD], page 57, for more information. Aside from its flexibility, the gnu linker is more helpful than other linkers in providing diagnostic information. Many linkers abandon execution immediately upon encountering an error, whenever possible, ld continues executing, allowing you to identify other errors (or, in some cases, to get an output file in spite of the error).en_US
dc.format.extent84tr.
dc.format.mimetypeapplication/pdf
dc.language.isoenen_US
dc.publisherJeffrey Osieren_US
dc.subjectGNU linkeren_US
dc.subjectUsing LDen_US
dc.subjectOpen Source Softwareen_US
dc.titleUsing LD the GNU linkeren_US
dc.typeBooken_US
dc.size497KBen_US
dc.departmentICTen_US


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record