Your message dated Mon, 5 Feb 2018 15:38:05 +0100
with message-id <56babf10-9d75-e0f9-135b-47dff5afe...@debian.org>
and subject line Re: Bug#843837: libxft-dev: Xft/Xft.h header incorrectly 
includes ft2build.h
has caused the Debian Bug report #843837,
regarding libxft-dev: Xft/Xft.h header incorrectly includes ft2build.h
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
843837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxft-dev
Version: 2.3.2-1
Severity: normal
Tags: upstream

Dear Maintainer,

   * What led up to the situation?
  Tried to build Motif from sources.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
  Take Motif sources and run configure && make

   * What was the outcome of this action?
  Compilation error:
make[3]: Entering directory '/home/alex/heap/motif.sf.git/lib/Xm'
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.
-I../../include -I.. -I./.. -DXMBINDDIR_FALLBACK=\"/usr/lib/X11/bindings\"
-DINCDIR=\"/usr/include/X11\" -DLIBDIR=\"/usr/lib/X11\"     -O0 -g3 -Wall -g
-fno-strict-aliasing -Wno-unused -Wno-comment -fno-tree-ter  -MT Label.lo -MD
-MP -MF .deps/Label.Tpo -c -o Label.lo Label.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../include -I.. -I./..
-DXMBINDDIR_FALLBACK=\"/usr/lib/X11/bindings\" -DINCDIR=\"/usr/include/X11\"
-DLIBDIR=\"/usr/lib/X11\" -O0 -g3 -Wall -g -fno-strict-aliasing -Wno-unused
-Wno-comment -fno-tree-ter -MT Label.lo -MD -MP -MF .deps/Label.Tpo -c Label.c
-fPIC -DPIC -o .libs/Label.o
In file included from XmRenderTI.h:33:0,
                 from Label.c:77:
/usr/include/X11/Xft/Xft.h:39:22: fatal error: ft2build.h: No such file or
directory
 #include <ft2build.h>
                      ^
compilation terminated.
Makefile:1048: recipe for target 'Label.lo' failed
make[3]: *** [Label.lo] Error 1
make[3]: Leaving directory '/home/alex/heap/motif.sf.git/lib/Xm'

   * What outcome did you expect instead?
  Motif should compile without errors.


/usr/include/X11/Xft/Xft.h from the package libxft-dev. This header has include
string:

....
#include <ft2build.h>
....

on line 39.

This is incorrect. Since ft2build.h is installed in
  /usr/include/freetype2
dir, the include macro must be the following:

  #include <freetype2/ft2build.h>




-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libxft-dev depends on:
ii  libc6-dev [libc-dev]   2.19-18+deb8u6
ii  libfontconfig1-dev     2.11.0-6.3+deb8u1
ii  libfreetype6-dev       2.5.2-3+deb8u1
ii  libx11-dev             2:1.6.2-3
ii  libxft2                2.3.2-1
ii  libxrender-dev         1:0.9.8-1+b1
ii  zlib1g-dev [libz-dev]  1:1.2.8.dfsg-2+b1

libxft-dev recommends no packages.

libxft-dev suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
On 02/04/2018 01:05 PM, Hugh McMaster wrote:
> Hi Graham,
> 
> Sorry for the delayed reply.
> 
> On Wednesday, 31 January 2018 5:23 PM, Graham Inggs wrote:
>> I saw this message in bug #887595 [1] and thought it would be relevant here:
>>
>> On Tue, Jan 23, 2018 at 11:56:38AM +0000, Hugh McMaster wrote:
>>> Also note that the Freetype2 developers no longer recommend using
>>>     #include <freetype2/ft2build.h>
>>> in source files (which was the intent of my patch). The following should be
>>> used instead:
>>>     #include <ft2build.h>
>>>     #include FT_FREETYPE_H
>>>
>>> Developers would then use either freetype-config or pkg-config to
>>> obtain the cflags etc.
>>
>> Hugh, do you have a reference for the above?
> 
> The freetype-2.8 API reference shows this #include usage.  Look at the 
> documentation
> provided with libfreetype6-dev in 
> /usr/share/doc/libfreetype6/documentation.html,
> particulary Tutorial #1 and Example #1.
> 
> Freetype-2.9 (the most recent upstream version) also has this information.
> See [1] for information on freetype2's header inclusion scheme and [2] for 
> the tutorial.
> 
> [1] 
> https://www.freetype.org/freetype2/docs/reference/ft2-header_inclusion.html
> [2] https://www.freetype.org/freetype2/docs/tutorial/step1.html
> [3] 
> https://anonscm.debian.org/cgit/collab-maint/motif.git/tree/debian/patches/fix_ac_find_xft.patch
> 

Closing this bug as invalid.

Cheers,
Julien

--- End Message ---

Reply via email to