[tex-k] Minor prototype fix in kpathsea header file

Tomas Rokicki rokicki at gmail.com
Sat Oct 19 02:15:35 CEST 2019

Doug, I'd be happy to help you; can we take this to private mail?

In any case easiest is to just build the whole tree.  Otherwise read the
instructions.  I have no trouble building on OS-X.

The relevant part of the instructions is right here, and that's likely all
need to know; this is from README.2building . . .

   If you want to work on a single program within the TL sources, this
is the recommended way to do it.  Here is an example from start to
finish for working on 'dvipdfm-x'.

     mkdir mydir && cd mydir  # new working directory

     # Get sources (<http://tug.org/texlive/svn>)
     rsync -a --delete --exclude=.svn --exclude=Work \
           tug.org::tldevsrc/Build/source/ .

     # Create build directory:
     mkdir Work && cd Work

     # Do the configure:
     ../configure --disable-all-pkgs --enable-dvipdfm-x \
       -C CFLAGS=-g CXXFLAGS=-g >&outc

     # Do the make:
     make >&outm

     # Test:
     cd texk/dvipdfm-x
     make check

On Fri, Oct 18, 2019 at 4:42 PM Doug McKenna <doug at mathemaesthetics.com>

> My goal is to compile the source code for `kpsewhich' to create my own
> private version (using XCode on a Mac) so I can single step through its
> operation with my debugger.
> In the kpathsea source code folder, there are two files, "configure" and "
> configure.ac".  The first looks to be a shell script, the second is in
> whatever language the ".ac" stands for.  Neither is runnable that I can
> tell (using `sh' or `bash'), and the README file with the kpathsea source
> code doesn't give any indication of how to do so.
> The documentation at <http://tug.org/texlive/doc/tlbuild.html> says
> something about running `configure' at a top-level, but I don't want to
> build an entire texlive.  Also, it's not clear what "running configure"
> means at any particular level.
> I can create the missing "HAVE_..." constants and "c-auto.h" file by hand
> if I have to, but meantime, I'm (obviously) confused.
> - Doug McKenna
> ----- Original Message -----
> From: "Karl Berry" <karl at freefriends.org>
> To: "doug" <doug at mathemaesthetics.com>
> Cc: "tex-k" <tex-k at tug.org>
> Sent: Friday, October 18, 2019 3:44:00 PM
> Subject: Re: [tex-k] Minor prototype fix in kpathsea header file
> The documentation says there's a
>     "kpathsea.h" file that references all the headers,
> It's created at build time. Guess I need to improve the documentation.
> E.g., if you run "./Build" in the TL Build/source subtree, it should end
> up at Build/source/Work/texk/kpathsea/kpathsea.h. I'll attach it.
>     But all the "HAVE_..." compilation constants aren't defined anywhere I
> They are defined by running configure. It's not possible to build the
> kpathsea source (or, indeed, basically anything in TL) without running
> configure. http://tug.org/texlive/doc/tlbuild.html
>     There's no "c-auto.h" file in the archive either, just a "c-auto.in"
> Again, it's created by configure. --best, karl.

--  http://cube20.org/  --  http://golly.sf.net/  --
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/tex-k/attachments/20191018/47626c76/attachment.html>

More information about the tex-k mailing list