public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: "Dale P. Smith" <dpsm@en.com>
To: ariel@arcavia.com, guile-gtk@sourceware.cygnus.com
Subject: Currnet CVS fails to configure
Date: Tue, 28 Nov 2000 09:17:00 -0000	[thread overview]
Message-ID: <00Nov28.121831est.17025@gateway.elms.k12.oh.us> (raw)

Greetings!

The current CVS guile-gtk fails to configure on my system, basically a
stock Debian Potato intel system, except for CVS guile.  Gtk+ is at 1.2.

I commented out some things in configure.in, as shown in the patch
below.  It now configures and builds just fine.  I'm not sure what's
missing, but I don't think I have any of that xxx_2_0 stuff on my
system.

-Dale


Index: configure.in
===================================================================
RCS file: /cvs/gnome/gnome-guile/guile-gtk/configure.in,v
retrieving revision 1.43
diff -c -r1.43 configure.in
*** configure.in	2000/11/19 22:29:05	1.43
--- configure.in	2000/11/28 17:11:10
***************
*** 15,28 ****
              [  --enable-debug          compile with -g for debugging
symbols],
              [ CFLAGS="-g $CFLAGS" ])
  
! AC_CHECK_PROG(GTK_CONFIG_2_0, gtk-config-2.0, yes, no)
  
! if test $GTK_CONFIG_2_0 = no; then
     AM_PATH_GTK(1.2.0,,AC_ERROR(need at least Gtk+ version 1.2),
gthread)
! else
!    AM_PATH_GTK_2_0(1.3.1,,AC_ERROR(need at least Gtk+ version 1.3.1),
gthread)   
!    AC_DEFINE(GTK_2_0)
! fi
  
  # XXX - gtk_config_*_version leaks from AM_PATH_GTK.
  
--- 15,28 ----
              [  --enable-debug          compile with -g for debugging
symbols],
              [ CFLAGS="-g $CFLAGS" ])
  
! dnl AC_CHECK_PROG(GTK_CONFIG_2_0, gtk-config-2.0, yes, no)
  
! dnl if test $GTK_CONFIG_2_0 = no; then
     AM_PATH_GTK(1.2.0,,AC_ERROR(need at least Gtk+ version 1.2),
gthread)
! dnl else
! dnl   AM_PATH_GTK_2_0(1.3.1,,AC_ERROR(need at least Gtk+ version
1.3.1), gthread)   
! dnl    AC_DEFINE(GTK_2_0)
! dnl fi
  
  # XXX - gtk_config_*_version leaks from AM_PATH_GTK.
  

-- 
Dale P. Smith
Altus Technologies Corp.
dsmith@altustech.com
440-746-9000 x309

             reply	other threads:[~2000-11-28  9:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-28  9:17 Dale P. Smith [this message]
2000-11-28 11:47 ` Marius Vollmer
2000-11-28 14:09   ` Ariel Rios
2000-11-28 15:02     ` Marius Vollmer
2000-11-28 15:12       ` Dale P. Smith
2000-11-28 15:31         ` Greg Troxel
2000-11-28 16:39           ` Dale P. Smith
2000-11-28 17:54           ` Ariel Rios
2000-11-29  5:29           ` Dale P. Smith
2000-11-28 15:40 ` Currnet CVS fails to configure - the patch Martin Baulig
2000-11-28 21:59   ` Ariel Rios
2000-11-28 22:27   ` Ariel Rios
2000-11-29  2:37     ` Martin Baulig
2000-11-29 10:39       ` Ariel Rios
2000-11-29 13:56         ` Martin Baulig
2000-11-29 14:54         ` Martin Baulig
2000-11-30 16:24     ` Marius Vollmer
2000-11-29  5:22   ` Lars J. Aas
2000-11-29  5:31     ` Martin Baulig
2000-12-02 22:12       ` Ariel Rios
2000-12-03  8:52         ` Martin Baulig
2000-12-03 20:32           ` Ariel Rios
2001-01-06 10:46             ` Marius Vollmer
2001-01-06 15:53               ` Ariel Rios
2001-01-13  4:10                 ` Marius Vollmer

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=00Nov28.121831est.17025@gateway.elms.k12.oh.us \
    --to=dpsm@en.com \
    --cc=ariel@arcavia.com \
    --cc=guile-gtk@sourceware.cygnus.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).