PERL,INGRES,PROGRAMMING

I wanted to set up a2ps 4.14 on an old SCO Unix machine (which suprsingly had a gcc compiler installed) for Transforming Ingres' legacy reports with PostScript  Before you set up a2ps, you have to set gperf up first. Its installation  was a breeze, so I assumed that a2ps would install easily too.....However that was not the case; when reaching the 'make' phase I was getting the following error : Making all in lib make all-am Making all in src make all-am /bin/ksh ../libtool --tag=CC --mode=link gcc -g -O2 -o a2ps main.o read.o sshread.o ssheet.o select.o generate.o delegate.o regex.o buffer.o ve rsions.o ffaces.o version-etc.o long-options.o parsessh.o lexssh.o lexps.o sh eets-map.o ../lib/liba2ps.la -lm gcc -g -O2 -o a2ps main.o read.o sshread.o ssheet.o select.o generate.o delegate .o regex.o buffer.o versions.o ffaces.o version-etc.o long-options.o parsessh.o lexssh.o lexps.o sheets-map.o ../lib/.libs/liba2ps.a -lm  ...

this : Plain text ASCII report (plain.jpg) into this : PostScript report (postscript.jpg) How things work at the moment: PC's with Windows OS run terminal emulators which connect to Unix/Linux servers. When the ABF application generates a report its output is dumped on disc as a plain text file which is subsequently send to a network or local printer. When local printing is required (the printer is attached locally to the PC running the emulator) then the emulator opens a direct connection to the local printer port by using special escapes (called transparent ot pass-thru printing) and then forwards the plain text file to it. In either case the file is forwarded to the printer in RAW format, bypassing any printer drivers and thus is printed as-is. The same process holds also true for reports generated by OpenRoad on Windows The disadvandes of this approach are : (1). although sent in RAW format, the interpretation lies on the printer at hand; for example some print...