Well, I'm confused now. There is no autogen.sh in the gtk+-2.14.2 directory.
Also, the config.h generated for gtk+-2.12.12 (with which gnubg compiled)
contains no GTK_DISABLE_DEPRECATED references either.
I simply grabbed the latest stable gtk+ tarball from their website,
uncompressed it, and followed the standard build and install instructions. I'm
not checking out unstable gtk+ code using svn.
Louis
On Tue, 23 Sep 2008 16:17:19 +0200
"Christian Anthon" <[EMAIL PROTECTED]> wrote:
Okay,
if the lines doesn't exist at all, your autotools files are in an
inconsistent state. Try running ./autogen.sh before configure.
Christian.
On Tue, Sep 23, 2008 at 4:13 PM, Louis Zulli <[EMAIL PROTECTED]> wrote:
On Sep 23, 2008, at 9:54 AM, Christian Anthon wrote:
I'm a bit mystified here. You should have lines in your config.h matching
these
/* Define if you want to disable deprecated gtk functions */
/* #undef GTK_DISABLE_DEPRECATED */
/* Define if you want to disable deprecated glib functions */
/* #undef G_DISABLE_DEPRECATED */
or similar lines where GTK_DISABLE_DEPRECATED is defined to be 1
Christian.
No such lines. Running configure did create config.h, and that file contains
lines where various flags are defined to be 1, but nothing even similar
to GTK_DISABLE_DEPRECATED appears. I'll investigate further when I leave
work later today. Clearly my configure is not doing what yours is doing!
Louis
_______________________________________________
Bug-gnubg mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnubg
