Bug#253958: (fwd) Re: (fwd) Bug#253958: Unable to build packages depending on this with gcc.

[Olaf Weber <olaf@infovore.xs4all.nl>]

Hilmar Preusse writes:
> On 14.06.04 Hilmar Preusse (hille42@web.de) wrote:

>> Perhaps we should more explicitly say, that one have to use
>> "#include <kpathsea/kpathsea.h>". I guess, that was the bug in that
>> case. Patch applies to kpathsea.texi of latest beta and teTeX 2.0.2

> What about this suggestion? If there is nothing more to add (i.e. you
> don't plan to change the docs) I suggest to close that bug now, as
> the issue is clarified.

FYI, I made the following change to the kpathsea sources.

infovore:/home/olaf/web2c/src/texk/texk/kpathsea$ cvs diff -ur1.55 -r1.56 kpathsea.texi
Index: kpathsea.texi
===================================================================
RCS file: /usr/local/cvsroot/texk/texk/kpathsea/kpathsea.texi,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -r1.55 -r1.56
--- kpathsea.texi       7 May 2004 19:46:13 -0000       1.55
+++ kpathsea.texi       14 Jun 2004 09:22:13 -0000      1.56
@@ -2016,8 +2016,17 @@
 files define the actual routines, which are the ultimate documentation).
 @file{pathsearch.h} declares the basic searching routine.
 @file{tex-file.h} and @file{tex-glyph.h} define the interfaces for
-looking up particular kinds of files.  You may wish to use
-@code{#include <kpathsea/kpathsea.h>}, which includes every Kpathsea header.
+looking up particular kinds of files.  In view of the way the headers
+depend on each other, it is recommended to use @code{#include
+<kpathsea/kpathsea.h>}, which includes every Kpathsea header.
+
+@flindex config.h
+@flindex c-auto.h
+If you want to include only specific headers, you should still consider
+including @file{kpathsea/config.h} before including any other Kpathsea
+header, as it provides symbols used in the other headers.  Note that
+@file{kpathsea/config.h} includes @file{kpathsea/c-auto.h}, which is
+generated by Autoconf.

 @cindex file types, registering new
 The library provides no way for an external program to register new file

-- 
Olaf Weber

               (This space left blank for technical reasons.)