Hi Martin, Hadi,
I did the same (checked my own config.log files) and observed the same
think like Martin. But it seems that the checking for.. lines are
only there for successful checks (look at other failed checks in
config log). Nevertheless I agree that it is strange that there's no
output at
I managed to get past this error using the following configuration line:
./configure --with-target-bits=64
--with-freetype-include=/usr/include/freetype2/
--with-freetype-lib=/usr/lib/x86_64-linux-gnu
It's good enough for us to be able to build, so I'll stick with it, but
it seems the
Glad to hear that you were able to build.
I think it's the multi-arch configuration on Linux which is still
broken, but that's just my opinion:)
Nevertheless you are probably right that the build system could
somehow work around this or at least spit out a clearer error message.
Regards,
Volker
Maybe this is a 32/64 bit mismatch - i.e. you are on a 64-bit machine
with 64-bit libfreetype but configuring for 32-bit ?
On Fri, Dec 19, 2014 at 10:08 AM, Cédric Champeau
cedric.champ...@gmail.com wrote:
Hi everyone,
Some of you may know that we try to test Groovy builds against the latest
Martin Buchholz martinrb@... writes:
Others don't seem to have this problem - you can try looking at
config.log and elsewhere trying to figure out what went wrong.
On Fri, Dec 19, 2014 at 1:08 AM, Cédric Champeau
cedric.champeau@... wrote:
Hi everyone,
Some of you may know that we
It's a mystery. My own successful config.log snippet with latest jdk8u is
below. Why didn't your config.log contain checking for FREETYPE? Maybe
a pkg-config problem? Are you doing something crazy like defining
LD_LIBRARY_PATH? Someone will need to debug configure, perhaps using bash
-x
Hi everyone,
Some of you may know that we try to test Groovy builds against the
latest versions of the JDK. For that, we have setup a CI build of
OpenJDK 7, 8 and 9. However, the JDK 8 builds have been failing for
several months now (sorry I didn't have much time to investigate this
specific
Others don't seem to have this problem - you can try looking at
config.log and elsewhere trying to figure out what went wrong.
On Fri, Dec 19, 2014 at 1:08 AM, Cédric Champeau
cedric.champ...@gmail.com wrote:
Hi everyone,
Some of you may know that we try to test Groovy builds against the
