A "complete" R6 or R5 implementation means that xmkmf and imake are configured and installed on your system, and that the Xaw and Xmu libraries and header files are installed. Some vendors (HP, IBM, SCO) consider these optional software and do not always install them.
If you are running vanilla X11R6 or X11R5, then the build procedure is to ensure that your X11 bin directory is in your $PATH, then:
./configure # probe for system dependencies and create the Imakefile xmkmf # create a Makefile make depend # add dependency information make # build x3270 and its fontsx3270 prefers that its fonts be installed in order to run. However, a script is provided for testing a local copy of x3270 in the current directory:
./dryrun # test x3270Once you are satisfied that x3270 is working, you can install it (as root) with the command:
make installBefore running x3270, you will also need to (once):
xset fp rehashThat's the easy way. Here are the exceptions:
After running xmkmf, edit the Makefile and change:
@@forto:
@for(there's only one).
Once these have been installed, you can use the standard X11R5 build procedure above.
A number of unsupported core MIT clients and miscellaneous utilities are provided in /usr/contrib/bin. In addition, the entire core MIT distribution, compiled for Hewlett-Packard platforms, can be obtained from HP's users group INTERWORKS for a nominal fee. See the release notes for details.What you need is the Xaw and Xmu libraries, imake, and xmkmf. Then you can follow the vanilla R5 build and install instructions.
Do not use Sun's "BSD-compatibility" C compiler, /usr/ucb/cc. This is good advice in general, and in particular, x3270 will not build under it. Unfortunately, if you have installed Sun's unbundled C compiler, and have /usr/ucb in your $PATH ahead of /usr/ccs/bin, then you will get /usr/ucb/cc by default. The fix is to install gcc (much preferred) or to have /usr/ccs/bin ahead of /usr/ucb in your $PATH.
If you are using gcc, then Sun's xmkmf configuration puts some compiler flags in the Makefile that are specific to Sun's unbundled C compiler, and you may get a number of harmless, but annoying error messages while compiling. To eliminate these, use the command:
make CDEBUGFLAGS=-O "CCOPTIONS=-DSYSV -DSVR4"To run x3270, you must have your LD_LIBRARY_PATH environment variable set properly. First, it must include /usr/openwin/lib.
cd into XXX.
For each .bdf file, run the server-specific version of bdftosnf or bdftopcf to create a .snf or .pcf file. For example, for to build an NCD font on a Sun-4, the command is:
/usr/local/NCD/binSun4/bdftosnf 3270.bdf >3270.snfRun the server-specific version of mkfontdir. For example:
/usr/local/NCD/binSun4/mkfontdir .Then tell your X server to use this directory:
xset fp+ XXX xset fp rehash
Unfortunately, using an app-defaults file is a pain. The mechanism for finding the file is so flexible as to be almost incomprehensible, and it is difficult to run the program without doing a full installation, requiring root access to your system. Also, the app-defaults file generally changes whenever the program changes, and making sure that x3270 finds the correct app-defaults file compounds the above problems.
Starting with version 3.1.0.0, x3270 no longer uses a separate app-defaults file. Instead, the file is compiled into x3270 itself. If however, you prefer to have a separate app-defaults file, you can compile x3270 to use it.
First, you must decide whether you want app-defaults for a color display or a monochrome display. For a color display, the commands are:
./configure --enable-app-defaults xmkmf make clean makeFor a monochrome display, the commands are:
./configure --enable-app-defaults=-UCOLOR xmkmf make clean make