From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Having problems compiling several packages, possible issues with pango?
Date: Mon, 05 Sep 2011 07:57:22 -0700 [thread overview]
Message-ID: <j42o0i$jfh$1@dough.gmane.org> (raw)
In-Reply-To: <CAG+b7UWfcjUMg=qBP7aquVoB9k5uQBdQcLqv0Dcu8hBueHhFWA@mail.gmail.com>
On 09/05/2011 03:29 AM, Datty wrote:
> Hi all,
>
> I've been having a few problems with a week old gentoo desktop install with gnome 3 from the gnome overlay. Both libgnomeprint-2.18.8 and evolution-3.0.3 are failing showing the errors below which I think are related to pango.
>
> In file included from /usr/include/pango-1.0/pango/pango-gravity.h:98:0,
> from /usr/include/pango-1.0/pango/pango-types.h:91,
> from /usr/include/pango-1.0/pango/pango-font.h:26,
> from /usr/include/pango-1.0/pango/pango-fontmap.h:25,
> from ../../libgnomeprint/gnome-font.h:73,
> from ../../libgnomeprint/gnome-print.h:59,
> from ../gnome-print-private.h:43,
> from sft.h:92,
> from crc32.c:47:
> /usr/include/pango-1.0/pango/pango-script.h:132:12: error: expected declaration specifiers or ‘...’ before ‘G_CONST_RETURN’
The guilty syntax (appearing in several pango headers) seems to be this:
G_CONST_RETURN char **start
^^^^
Looking at the vast number of uses of G_CONST_RETURN in other header files,
I'm guessing that the word 'char' should really be 'gchar'.
I would test this idea by editing the headers in /usr/include/pango-1.0/pango
by hand, making the above change to every instance of 'C_CONST_RETURN char'.
If that trick works, then it's definitely a bug in the pango package and
needs to be fixed. Otherwise, I'm stumped.
next prev parent reply other threads:[~2011-09-05 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 10:29 [gentoo-user] Having problems compiling several packages, possible issues with pango? Datty
2011-09-05 14:57 ` walt [this message]
2011-09-06 8:11 ` [gentoo-user] " Datty
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='j42o0i$jfh$1@dough.gmane.org' \
--to=w41ter@gmail.com \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox