EXAMPLES

To setup lbxproxy, start the X server as usual, and then start the proxy. The lbxproxy is a pseudo-server, so any clients that wish to use it need to adjust their DISPLAY. By default, the proxy will listen on <hostname>:1. This can be changed with the :displaynumber argument.

If the proxy is to be running on a host named sharedhost, connecting to an LBX-capable X server on a desktop machine named mydesktop, you could use the following command to start the proxy (which would be known as display sharedhost:7):

mydesktop% rlogin sharedhost

sharedhost% lbxproxy -display mydesktop:0 :7 &

sharedhost% xclient -display sharedhost:7

If you are running LBX over a TERM connection between mydesktop and sharedhost, try something like this:

mydesktop% trsh

sharedhost% tredir -r 6008 6000

sharedhost% lbxproxy -display sharedhost:8 :7 &

sharedhost% xclient -display sharedhost:7

SEE ALSO

General information: X(1)

Server-specific man pages: Xserver(1), Xdec(1),

XmacII(1), Xsun(1), Xnest(1), Xvfb(1), XF86_Accel(1),

XF86_Mono(1), XF86_SVGA(1), XF86_VGA16(1), XFree86(1)

AUTHORs

The LBX team includes Dave Lemke, Dale Tonogai, Keith Packard, Jim Fulton from NCD, and Chris Kanterjiev from Xerox.

X Version 11 Release 6

ld

ld—The GNU linker

SYNOPSIS

ld [ _o.I output ] .I objfile . . . .br .RB ["_A output ] objfile ...

[_A architecture ][_b\ input-format ][_Bstatic ][_c\ commandfile ]

[ _d|_dc|_dp ]

[ _defsym\ symbol = expression ][_e\ entry ][_F ][_F\ format ][_

format\ input-format ][_g ][_G size ][--help ][_i ][_l ar ][_

L searchdir ][_M][_Map mapfile ][_m emulation ][_n|_N][_

noinhibit-exec ][_oformat\ output-format ][_R\ filename ][_relax ]

[ _r|_Ur][_S ][_s ][_sort_common][_T\ commandfile ][_Ttext\

textorg ][_Tdata\ dataorg ][_Tbss\ bssorg ][_t ][_u\ sym ][_V ][_

v][--verbose ][--version ][_warn_common][_warn_once][_X ]

[ _x ]

DESCRIPTION

ld combines a number of object and archive FILES, relocates their data, and ties up symbol references. Often the last step in building a new compiled program to run is a call to ld.

ld accepts Linker Command Language FILES to provide explicit and total control over the linking process. This man page does not describe the command language; see the ld entry in info, or the manual Ld: The GNU Linker, for full details on the command language and on other aspects of the GNU linker.

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. You can use objdump _i to get a list of FORMATS supported on various architectures; see objdump(1).

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).

The GNU linker ld is meant to cover a broad range of situations, and to be as compatible as possible with other linkers. As a result, you have many choices to control its behavior through the command line, and through ENVIRONMENT variables.

OPTIONS

The plethora of command-line OPTIONS may seem intimidating, but in actual practice few of them are used in any particular context. For instance, a frequent use of ld is to link standard UNIX object FILES on a standard, supported UNIX system. On such a system, this line links a file hello.o :

$ ld _o output /lib/crt0.o hello.o _lc

This tells ld to produce a file called output as the result of linking the file /lib/crt0.o with hello.o and the library libc.a, which will come from the standard search directories.

The command-line OPTIONS to ld may be specified in any order, and may be repeated at will. For the most part, repeating an option with a different argument will either have no further effect or override prior occurrences (those further to the left on the command line) of an option.

The exceptions—which may meaningfully be used more than once—are _A, _b (or its synonym _format), _defsym, _L, _l, _R, and _u.

The list of object FILES to be linked together, shown as objfile, may follow, precede, or be mixed in with command-line OPTIONS, except that an objfile argument may not be placed between an option flag and its argument.

Usually the linker is invoked with at least one object file, but other forms of binary input FILES can also be specified with _l,
_R, and the script command language. If no binary input FILES at all are specified, the linker does not produce any output, and issues the message No input FILES.

Option arguments must either follow the option letter without intervening whitespace or be given as separate arguments immediately following the option that requires them.