![](https://secure.gravatar.com/avatar/58cce501a997822a0cb6051496d1b0c8.jpg?s=120&d=mm&r=g)
Hi, the cross-compiled djgpp binaries aborted when trying to create some PK font (most probably because the font being used doesn't have a corresponding entry in the map files). The log file says:
Assertion failed at /home/thanh/pdftex/src/thanh/texk/kpathsea/tex-make.c line 5 1: dpi != 0 && bdpi != 0 Exiting due to signal SIGABRT
Does anyone have an idea what to do here? I remember this problem was reported sometime ago, but not sure whether anything has been done with it. The quick fix seems to disable auto-generating PK fonts with cross-compiled DJGPP. Thanh
![](https://secure.gravatar.com/avatar/b6331822ffe41d6f43aa40081bf7eaca.jpg?s=120&d=mm&r=g)
The Thanh Han writes:
Hi, the cross-compiled djgpp binaries aborted when trying to create some PK font (most probably because the font being used doesn't have a corresponding entry in the map files). The log file says:
Assertion failed at /home/thanh/pdftex/src/thanh/texk/kpathsea/tex-make.c line 5 1: dpi != 0 && bdpi != 0 Exiting due to signal SIGABRT
Does anyone have an idea what to do here? I remember this problem was reported sometime ago, but not sure whether anything has been done with it. The quick fix seems to disable auto-generating PK fonts with cross-compiled DJGPP.
Somehow both the environment variables KPATHSEA_DPI and MAKETEX_BASE_DPI are not set. As a result, the kpathsea library doesn't know which parameters to pass to mktexpk. It is very likely that MAKETEX_BASE_DPI in particular is what you're missing. It is normally set by calling kpse_init_prog(). -- Olaf Weber (This space left blank for technical reasons.)
![](https://secure.gravatar.com/avatar/ad5afbb91c8b5ec2b1199838461a8348.jpg?s=120&d=mm&r=g)
On Mon, 1 Nov 2004, Olaf Weber wrote:
Somehow both the environment variables KPATHSEA_DPI and MAKETEX_BASE_DPI are not set. As a result, the kpathsea library doesn't know which parameters to pass to mktexpk.
maybe it has to do with the thread [NTG-pdftex] Automatic pk generation, 11 Dec. 2003 Regards, Hartmut
![](https://secure.gravatar.com/avatar/58cce501a997822a0cb6051496d1b0c8.jpg?s=120&d=mm&r=g)
Hi, yes I have also looked into tex-make.c and seen that KPATHSEA_DPI and MAKETEX_BASE_DPI are environment variables that are not set for some reason. this happens only with cross-compiled pdftex, so perhaps something that usually works under UNIX/DOS is not working here? Anyway, I suggest to disable auto-generating pk fonts with cross-compiled pdftex. But I don't know how I can test whether I am using a cross-compiler inside tex-make.c. Thanh PS: sorry about the empty subject in the previous post. On Mon, Nov 01, 2004 at 12:16:33PM +0100, Olaf Weber wrote:
The Thanh Han writes:
Hi, the cross-compiled djgpp binaries aborted when trying to create some PK font (most probably because the font being used doesn't have a corresponding entry in the map files). The log file says:
Assertion failed at /home/thanh/pdftex/src/thanh/texk/kpathsea/tex-make.c line 5 1: dpi != 0 && bdpi != 0 Exiting due to signal SIGABRT
Does anyone have an idea what to do here? I remember this problem was reported sometime ago, but not sure whether anything has been done with it. The quick fix seems to disable auto-generating PK fonts with cross-compiled DJGPP.
Somehow both the environment variables KPATHSEA_DPI and MAKETEX_BASE_DPI are not set. As a result, the kpathsea library doesn't know which parameters to pass to mktexpk.
It is very likely that MAKETEX_BASE_DPI in particular is what you're missing. It is normally set by calling kpse_init_prog().
participants (3)
-
Hartmut Henkel
-
Olaf Weber
-
The Thanh Han