From: David Pirotte <david@altosw.be>
To: Ariel Rios <ariel@gnu.org>
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: gnome-guile-0.21pre2
Date: Tue, 21 Aug 2001 02:47:00 -0000 [thread overview]
Message-ID: <3B8222F7.C375DA9D@altosw.be> (raw)
In-Reply-To: <998368367.30770.38.camel@soleil>
Ariel Rios wrote:
> CAn you please check it now?
> All traces off pck-config should be gone now
still the same! am I doing the right thing when updating from cvs? here is what I
did: (rm -rf guile-gtk and gnome-guile, i don't trust update)
david@faust:~/ftp/guile $ export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'
david@faust:~/ftp/guile $ cvs login [no passwd, just enter]
david@faust:~/ftp/guile $ cvs -z3 checkout gnome-guile
david@faust:~/ftp/guile $ cvs -z3 checkout guile-gtk
david@faust:~/ftp/guile/guile-gtk $ sh ./autogen.sh
...
creating libtool
updating cache ./config.cache
loading cache ./config.cache
checking how to run the C preprocessor... gcc -E
checking for pkg-config... yes
./configure: line 2092: syntax error near unexpected token `GNOME_PKGCONFIG_CHECK_MODULES(GTK,'
./configure: line 2092: ` GNOME_PKGCONFIG_CHECK_MODULES(GTK, gtk+-2.0:1.3.1 gthread-2.0:1.3.1)'
david@faust:~/ftp/guile/guile-gtk $
david
next prev parent reply other threads:[~2001-08-21 2:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0108171224530.13635-100000@www.linuxppc.org>
[not found] ` <3B816605.30A94BAD@altosw.be>
2001-08-20 22:01 ` gnome-guile-0.21pre2 Ariel Rios
2001-08-20 22:27 ` gnome-guile-0.21pre2 Ariel Rios
2001-08-21 5:57 ` gnome-guile-0.21pre2 David Pirotte
2001-08-20 22:36 ` gnome-guile-0.21pre2 Ariel Rios
2001-08-21 2:47 ` David Pirotte [this message]
2001-08-21 9:13 ` gnome-guile-0.21pre2 Ariel Rios
2001-08-16 22:43 gnome-guile-0.21pre2 Ariel Rios
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=3B8222F7.C375DA9D@altosw.be \
--to=david@altosw.be \
--cc=ariel@gnu.org \
--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).