unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guix@gnu.org
Subject: Pango
Date: Fri, 14 Jun 2013 23:25:07 +0200	[thread overview]
Message-ID: <201306142325.07791.andreas@enge.fr> (raw)
In-Reply-To: <87r4g4dge7.fsf@gnu.org>

Am Freitag, 14. Juni 2013 schrieb Ludovic Courtès:
> All this sounds like an indication that we won’t be able to make much
> out of this test suite.  I would disable it

Okay; I just pushed cairo without tests.

Now the problem is pango. It finds cairo, but ends up with

checking for pkg-config... /nix/store/jdr6v3aqsy0bw74rwac8g77a2qag81ra-pkg-
config-0.27.1/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for HARFBUZZ... no
no
checking for CoreText availability... no
checking for CAIRO... yes
checking which cairo font backends could be used... none
configure: Disabling cairo support
configure: error: *** Could not enable any backends.
*** Must have at least one backend to build Pango.

Without saying so, pango seems to depend on harfbuzz on gnu/linux (on 
macosx it uses quartz, for windows there are other tests); but we need 
fontconfig/freetype, which is not even searched for without harfbuzz, 
according to the configure.ac:

#
# Check for fontconfig
#
have_fontconfig=false
if $have_harfbuzz ; then
  PKG_CHECK_MODULES(FONTCONFIG, fontconfig >= 2.10.91, 
have_fontconfig=true, AC_MSG_RESULT([no]))
fi
#
# Checks for FreeType
#
have_freetype=false
if $have_fontconfig ; then
  # The first version of freetype with a .pc file is 2.1.5.  That's recent
  # enough for all the functions we use I guess.  No version check needed.
  PKG_CHECK_MODULES(FREETYPE, freetype2, have_freetype=true, 
AC_MSG_RESULT([no]))
fi

This dependency is new since pango 1.31; I might go back to version 1.30, 
for which there is a recipe in nix.

Or try to compile harfbuzz; but the current version 0.9.18 fails its tests 
with endless error messages such as
test_unicode-test-unicode.o:(.rodata+0x1d0): undefined reference to 
`hb_unicode_script'

Version 0.9.4 (for which there is a recipe in nix) compiles and passes its 
tests. This looks like a need for bisection...

Enough for tonight,

Andreas

  reply	other threads:[~2013-06-14 21:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13 21:19 Demain Andreas Enge
2013-06-13 21:37 ` Demain Andreas Enge
2013-06-13 23:49   ` Demain Cyril Roelandt
2013-06-14  7:52     ` Demain Andreas Enge
2013-06-14 12:29   ` Demain Ludovic Courtès
2013-06-14 21:25     ` Andreas Enge [this message]
2013-06-14 21:34       ` Pango Andreas Enge
2013-06-15  8:12         ` Pango Andreas Enge
2013-06-15  8:29           ` Pango Andreas Enge
2013-06-15 13:17           ` Pango Ludovic Courtès
2013-06-15 13:31             ` Pango Andreas Enge
2013-06-15 13:49               ` Pango Ludovic Courtès
2013-06-15 14:07                 ` Pango Andreas Enge
     [not found]                   ` <87sj0j3yzh.fsf@gnu.org>
2013-06-15 20:55                     ` Pango Andreas Enge
2013-06-15 12:57         ` Pango Ludovic Courtès
2013-06-15  1:58       ` Pango Cyril Roelandt
2013-06-15  7:13         ` Pango Andreas Enge
2013-06-15 13:14           ` Pango Ludovic Courtès
2013-06-15 12:56       ` Pango Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201306142325.07791.andreas@enge.fr \
    --to=andreas@enge.fr \
    --cc=bug-guix@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).