Opened 10 years ago
Closed 6 years ago
#2491 closed defect (wontfix)
configure: error: *** Unable to locate FreeType includes.
Reported by: | strk | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 7.0.7 |
Component: | Compiling | Version: | unspecified |
Keywords: | Cc: | ||
CPU: | Unspecified | Platform: | Unspecified |
Description
Configuration of grass-7.0.0beta3 sources fail with:
checking whether to use FreeType... yes checking for location of FreeType includes... checking for ft2build.h... no configure: error: *** Unable to locate FreeType includes.
I have the file in /usr/include/freetype2/ft2build.h
Adding --with-freetype-includes=/usr/include/freetype2 switch fixes the configuration, but I'm wondering if the detector could do a better job by also looking in there, being the default install on ubuntu 14.04
NOTE: 7.0.0beta3 is missing a Version (would it be trunk?)
Change History (9)
comment:1 by , 10 years ago
follow-up: 5 comment:2 by , 10 years ago
$ freetype-config --cflags -I/usr/include/freetype2
Is that acceptable by policy then ?
comment:3 by , 10 years ago
That is (with proper trac syntax):
[strk@cdb:~] freetype-config --cflags -I/usr/include/freetype2
comment:4 by , 10 years ago
Replying to strk:
Adding --with-freetype-includes=/usr/include/freetype2 switch fixes the configuration
FWIW, the same is needed on Fedora 20.
comment:5 by , 10 years ago
Replying to strk:
$ freetype-config --cflags -I/usr/include/freetype2
Is that acceptable by policy then ?
Yes. But the configure script doesn't currently use freetype-config.
Before making that change, we should decide whether to use freetype-config or pkg-config.
Also, we don't currently have a macro for *-config scripts; each package which uses them has the same boilerplate.
comment:6 by , 9 years ago
Milestone: | 7.0.0 → 7.0.5 |
---|
comment:7 by , 8 years ago
Milestone: | 7.0.5 → 7.0.6 |
---|
comment:8 by , 7 years ago
Milestone: | 7.0.6 → 7.0.7 |
---|
As a matter of policy, configure doesn't add directories to the header or library search paths automatically. It only adds directories which are either specified by the user or obtained from pkg-config or package-specific config scripts (e.g. gdal-config).