From: Tomi Manninen <oh2bns@sral.fi>
To: richard <richard.bown@blueyonder.co.uk>
Cc: Linux-hams List <linux-hams@vger.kernel.org>
Subject: Re: another gmfsk compile prob
Date: Wed, 11 Jan 2006 21:28:32 +0200 [thread overview]
Message-ID: <1137007712.2683.3.camel@oh2bns.ampr.org> (raw)
In-Reply-To: <43C4E708.3050005@blueyonder.co.uk>
On Wed, 2006-01-11 at 13:07, richard wrote:
> ...
> In file included from /usr/include/gtk-2.0/gdk/gdk.h:50,
> from /usr/include/gtk-2.0/gtk/gtk.h:31,
> from /usr/include/libgnomeui-2.0/gnome.h:4,
> from ../../src/main.h:32,
> from mfsktx.c:42:
> /usr/include/gtk-2.0/gdk/gdkscreen.h:51: error: syntax error before
> 'cairo_font_options_t'
> ...
This is really strange. To me it looks like the (gdk?) libraries/
headers are broken in this machine. All gmfsk does here is
#include <gnome.h> and it results in this...
Does any other gnome app compile cleanly on this machine?
--
Tomi Manninen / OH2BNS / KP20JF74
prev parent reply other threads:[~2006-01-11 19:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 11:07 another gmfsk compile prob richard
2006-01-11 19:28 ` Tomi Manninen [this message]
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=1137007712.2683.3.camel@oh2bns.ampr.org \
--to=oh2bns@sral.fi \
--cc=linux-hams@vger.kernel.org \
--cc=richard.bown@blueyonder.co.uk \
/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