From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: a.out output Date: 20 Mar 2000 17:28:31 GMT Organization: Aachen University of Technology (RWTH) Lines: 30 Message-ID: <8b5n3v$lt2$1@nets3.rz.RWTH-Aachen.DE> References: <38D5EC8F DOT 6F64EDD4 AT deakin DOT edu DOT au> <38D60F30 DOT E206C28F AT deakin DOT edu DOT au> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 953573311 22434 137.226.32.75 (20 Mar 2000 17:28:31 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 20 Mar 2000 17:28:31 GMT User-Agent: tin/1.4-19991113 ("No Labels") (UNIX) (Linux/2.0.0 (i586)) Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eric Dines wrote: > That Chris Mears was really trying to be helpful, but didn't quite hit > the spot. Nor did your original question define the spot to be hit all too precisely... > Flat binary only is what we want, the files can then be linked up later > on another system. 'Flat binary' and 'linked ... later' are a contradiction to each other. Flat binary means that no 'control information' is in the file, just raw executable code and data. Stuff like addresses that the linker will have to fix up for relocating the code to its final position would be missing, i.e. you cannot possibly 'link' this to anything else, later. DJGPP tools can generate flat binary, in principle. See 'objcopy --help' and 'objdump -i' output for some details, and/or read the full binutils documentation in 'info'. > (Subtle differences in object files from elf/a.out systems are what is > causing the grief. ) You should re-think your strategy, and ask more clearly *what* you want, and why. Your question has been rather vague, so far. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.