Bugzilla Bug 29721

Looks like /usr/include/kpathsea isn't in the include path: 
 
# emerge app-text/dvipdfm 
Calculating dependencies ...done! 
>>> emerge (1 of 1) app-text/dvipdfm-0.13.2c to / 
>>> md5 src_uri ;-) dvipdfm-0.13.2c.tar.gz 
>>> Unpacking source... 
>>> Unpacking dvipdfm-0.13.2c.tar.gz to /var/tmp/portage/dvipdfm-0.13.2c/work 
>>> Source unpacked. 
creating cache ./config.cache 
checking for gcc... gcc 
checking whether the C compiler (gcc -mcpu=athlon-xp -O3 -pipe ) works... yes 
checking whether the C compiler (gcc -mcpu=athlon-xp -O3 -pipe ) is a 
cross-compiler... no 
checking whether we are using GNU C... yes 
checking whether gcc accepts -g... yes 
checking for a BSD compatible install... /bin/install -c 
checking whether ln -s works... yes 
checking whether make sets ${MAKE}... yes 
checking whether you have kpathsea headers and they whether they know about 
the required file formats... no 
configure: error: PS_HEADER and/or VF formats not found in Kpathsea header 
files. 
 
This version of dvipdfm requires that kpathsea and its headers be installed. 
If you are sure they are installed and in a standard place, maybe you need a 
newer version of kpathsea?  You also might try setting the environment 
variable CPPFLAGS (or CFLAGS) with -I pointing to the directory containing 
the file tex-file.h 
 
 
 
!!! ERROR: app-text/dvipdfm-0.13.2c failed. 
!!! Function econf, Line 324, Exitcode 1 
!!! econf failed 

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

okay, the kpathsea library/headers are included in tetex, which version of
tetex do you have installed ? and can you try updating to tetex-2.0.2 if
you're on 1.0.7?

I have app-text/tetex-2.0.2-r1, and /usr/include/kpathsea/ is populated with
.h files.

-- Stephen

This binary, I just found out, is included in tetex-2.0.2, which has build
fine on my system. Maybe this ebuild is for those with an earlier version
of tetex?

This is closeable. Thanks for looking at it.

Stephen

No problem looking at your problem. But I think we have another problem here
if tetex-2 provides dvipdfm, which it does.

Usata: can dvipdfm depend =tetex-1, or is the support in tetex-2 not great
enough that it warrants including seperately ? (in that case we really need
tetex-2 to not include it's own dvipdfm and depend on the external ebuild).

Thanks.

this a ping to usata, because he was just added to the text-markup CC list.

Hi I got a mail from text-markup@g.o ;-)

dvipdfm is now developed within tetex distribution and they don't
release dvipdfm separately, so there's no point to remove dvipdfm
from app-text/tetex-2.0.2. I vote for putting DEPEND="=app-text/tetex-1*"
to dvipdfm ebuild.

FYI: I exclude dvipdfm from app-text/ptex ebuild just because I want
ptex to depend on dvipdfmx rather than dvipdm. (dvipdfm can't handle
cjk characters)

My sentiments exactly usata, agreed. I've updated dvipdfm to depend on tetex-1.