<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>29721</bug_id>
          
          <creation_ts>2003-09-26 21:58 0000</creation_ts>
          <short_desc>dvipdfm ebuild fails looking for kpathsea</short_desc>
          <delta_ts>2003-10-02 05:42:46 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Applications</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>stephen@theboulets.net</reporter>
          <assigned_to>text-markup@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>stephen@theboulets.net</who>
            <bug_when>2003-09-26 21:58:15 0000</bug_when>
            <thetext>Looks like /usr/include/kpathsea isn&apos;t in the include path: 
 
# emerge app-text/dvipdfm 
Calculating dependencies ...done! 
&gt;&gt;&gt; emerge (1 of 1) app-text/dvipdfm-0.13.2c to / 
&gt;&gt;&gt; md5 src_uri ;-) dvipdfm-0.13.2c.tar.gz 
&gt;&gt;&gt; Unpacking source... 
&gt;&gt;&gt; Unpacking dvipdfm-0.13.2c.tar.gz to /var/tmp/portage/dvipdfm-0.13.2c/work 
&gt;&gt;&gt; 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.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>obz@gentoo.org</who>
            <bug_when>2003-09-28 22:29:11 0000</bug_when>
            <thetext>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&apos;re on 1.0.7?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>stephen@theboulets.net</who>
            <bug_when>2003-09-29 05:32:18 0000</bug_when>
            <thetext>I have app-text/tetex-2.0.2-r1, and /usr/include/kpathsea/ is populated with
.h files.

-- Stephen</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>stephen@theboulets.net</who>
            <bug_when>2003-10-01 06:22:22 0000</bug_when>
            <thetext>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</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>obz@gentoo.org</who>
            <bug_when>2003-10-01 09:47:28 0000</bug_when>
            <thetext>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&apos;s own dvipdfm and depend on the external ebuild).

Thanks.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>obz@gentoo.org</who>
            <bug_when>2003-10-01 10:00:50 0000</bug_when>
            <thetext>this a ping to usata, because he was just added to the text-markup CC list.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>usata@gentoo.org</who>
            <bug_when>2003-10-01 11:40:06 0000</bug_when>
            <thetext>Hi I got a mail from text-markup@g.o ;-)

dvipdfm is now developed within tetex distribution and they don&apos;t
release dvipdfm separately, so there&apos;s no point to remove dvipdfm
from app-text/tetex-2.0.2. I vote for putting DEPEND=&quot;=app-text/tetex-1*&quot;
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&apos;t handle
cjk characters)
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>obz@gentoo.org</who>
            <bug_when>2003-10-02 05:42:46 0000</bug_when>
            <thetext>My sentiments exactly usata, agreed. I&apos;ve updated dvipdfm to depend on tetex-1.</thetext>
          </long_desc>
      
    </bug>

</bugzilla>