This version of gsftopk had been designed to be compiled on the amiga with
the SAS/C 6.58 compiler. It had be tested with amiweb2c-7.0 and, since it
uses the kpathsea library, may not work with other TeX implementations.


To build gsftopk you need:

- an amiga ;)
- SAS/C 6.57 or 6.58 (any version 6.5x should be ok)
- the kpathsea library (available on CTAN)


Building process:

- do not use configure but the supplied smakefile instead,
- edit smakefile and change EXECPATH and KPATHINCDIR according to your
  installation,
- run smake.

The smakefile will compile gsftopk and then install it in the right place.
It shouldn't be possible make it work from the source directory since
kpathsea uses the executable location to find the TDS tree.


Known bugs:

I used version 1.13 for a couple of months without problems *but* I
notice two cases leading to crashes. Paul Vojta is absolutly *not*
responsible for them.

gsftopk runs gs in background before trying to read the .tfm file. If the
tfm file is not found the gs is left running in background and, sadly, is
likely to crash the machine, soon. Since there is no efficient kill for
process on amiga and since I don't have much time to work on it you may
have to live with it, sorry.

I notice that, sometime, on some fonts, gsftopk crashes when exiting.
Fortunately I link with ccatch.o and you only get a requester asking you if
you want to make a snapshot. You can 'ok' or 'cancel' it, there will be no
consequence and no crash. I notice that it only happened when trying to
work on fonts with a name longer than nine characters. So I *suspect* a bug
in the current version of the kpathsea library. I have to investigate in
this direction.

Christophe Labouisse (gabuzo@mail.dotcom.fr)
