Seems like it's missing freetype2. plashFTFont.cc:15:22: error: ft2build.h: No such file or directory SplashFTFont.cc:16:10: error: #include expects "FILENAME" or <FILENAME> SplashFTFont.cc:17:10: error: #include expects "FILENAME" or <FILENAME> SplashFTFont.cc:18:10: error: #include expects "FILENAME" or <FILENAME> In file included from SplashFTFont.cc:24: Fix: Patch attached with submission follows: How-To-Repeat: tinderbox global options: INSTALL_NODEBUG="yes" A4=yes WITH_UTF8=yes WITHOUT_X11=yes WITHOUT_X=yes build-specific options: PERL_VERSION=5.12.4 NOPORTDOCS=yes port-options: # This file is auto-generated by 'make config'. # No user-servicable parts inside! # Options for xpdf-nox11-3.02_11 _OPTIONS_READ=xpdf-nox11-3.02_11 WITHOUT_LIBPAPER=true WITH_DRAW=true WITHOUT_X11=true
Responsible Changed From-To: freebsd-ports-bugs->araujo Over to maintainer (via the GNATS Auto Assign Tool)
I came across this too, it is probably a dupe of ports/169196 as well. It seems if you try to compile xpdf with X11 support disabled, it cannot find files from freetype2 even though they are installed. One imperfect but likely useful workaround would be to move the two freetype --configure lines into the section of the Makefile that is conditional on X11. At the very least, can it be marked conditionally BROKEN on WITHOUT_X11 (cannot find freetype when X11 support disabled) so more people don't spend more time debugging this? Although it would be better to make the freetype --configure lines conditional so we get something instead of nothing. I am trying to compile this on a webserver which needs pdftotext but not xpdf or any other X11 support. I'm trying to avoid adding X components on my webserver and I don't benefit from freetype support in the pdftotext binary. Thanks.
Hello guys, First of all, I'm sorry, I'm so busy these days that I couldn't take a look on this PR! However, I'm gonna check it tonight and maybe call you guys to make some tests in case I have some doubt about the fix. Thanks by the report. - Araujo 2012/10/7 Adam McDougall <mcdouga9@egr.msu.edu> > I came across this too, it is probably a dupe of ports/169196 as well. It > seems if you try to compile xpdf with X11 support disabled, it cannot find > files from freetype2 even though they are installed. One imperfect but > likely useful workaround would be to move the two freetype --configure > lines into the section of the Makefile that is conditional on X11. > > At the very least, can it be marked conditionally BROKEN on WITHOUT_X11 > (cannot find freetype when X11 support disabled) so more people don't spend > more time debugging this? Although it would be better to make the freetype > --configure lines conditional so we get something instead of nothing. > > I am trying to compile this on a webserver which needs pdftotext but not > xpdf or any other X11 support. I'm trying to avoid adding X components on > my webserver and I don't benefit from freetype support in the pdftotext > binary. Thanks. > -- Marcelo Araujo araujo@FreeBSD.org
Am Mon, 8 Oct 2012 16:44:17 +0800 schrieb Marcelo Araujo <araujobsdport@gmail.com>: > Hello guys, > > First of all, I'm sorry, I'm so busy these days that I couldn't take > a look on this PR! > However, I'm gonna check it tonight and maybe call you guys to make > some tests in case I have some doubt about the fix. Hi, sorry for not replying earlier, too. My bugreport is indeed a dupe (saw this later). The fix in the other PR does work (for me). Regards, Rainer
State Changed From-To: open->closed Committed, with minor changes. Thanks!