Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ omerge(8) — AOS 4.3

Media Vault

Software Library

Restoration Projects

Artifacts Sought

OMERGE(8)  —  

NAME

omerge − merge object files

SYNOPSIS

omerge [ −p# ] [ −D ] [ −l# ] [ −# ] input output

DESCRIPTION

Omerge takes two a.out files -- an input file and an output file -- and merges the input file into the output file. This merge makes sense only if space for the input file has been allocated in the output file. 

Omerge is generally used to combine two a.out files that cannot be linked by ld in the normal fashion, typically because they are linked to different base addresses, or when one module depends upon the content of the other (such as a built-in symbol table). The current uses for omerge are:

• To combine debugger symbol tables with the module (the symbol table cannot be produced until after the link)

• To combine a debugger (linked for physical addresses) and a kernel (linked for virtual addresses)

The following switches are accepted:

-p# Sets the logical page size, which is required to process ZMAGIC (demand-paged) files properly when cross linking. 

-D Prints internal debugging information about what omerge is doing. 

-l# Specifies a length that the input file cannot exceed. 

-# Specifies a hex offset at which the input file is placed in the output file. If no offset is specified, “0” is assumed. 

DIAGNOSTICS

switch %s not recognized
usage: %s infile outfile
cannot open %s for input
cannot open %s for input/output
%s: header too short
%s: bad header type
%s: header too short
%s: bad header type
input file exceeds available space by %d bytes
%s: read error
%s: file too short
%s: write error

PRPQs 5799-WZQ/5799-PFF: IBM/4.3  —  15 Dec 1986

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026