From: David Pirotte <david@altosw.be>
To: Ariel Rios <ariel@gnu.org>
Cc: Ariel Rios <ariel@linuxppc.org>, guile-gtk@sourceware.cygnus.com
Subject: Re: gnome-guile-0.21pre2
Date: Tue, 21 Aug 2001 05:57:00 -0000 [thread overview]
Message-ID: <3B824F6C.417AE0FF@altosw.be> (raw)
In-Reply-To: <998367824.1512.36.camel@soleil>
Ariel Rios wrote:
>
> On 20 Aug 2001 23:58:18 -0400, Ariel Rios wrote:
> > On 20 Aug 2001 21:33:25 +0200, David Pirotte wrote:
> > > ariel@www.linuxppc.org wrote:
> > > > ... gnome-guile-0.21pre2
> > >
> > > I've just installed glib-1.2.10 and gtk+-1.2.10
> > >
> > > trying to compile gnome-guile-0.21pre2 (configure was ok), i get the
> > > following error:
> > >
> > darn.. I cannot reproduce it here.
> > Do you have Gtk+ properly installed?
> maybe... just maybe you don't have guile 1.5 (or from CVS)
yes, maybe! I don't understand because I 'cvs co' everyday a guile-core
version, configure/compile/install ... and this only produced a 1.4.1 branch
so, I downloaded guile-core-20010821 snapshot, which does produce a branch
1.5.1 ?!?
everything is fine with configure/compile/install now, i'll test it with my
little gui ...
thanks a lot and sorry
david
are the cvs guile and gnome-guile co procedures on guile web pages
accurate?
next prev parent reply other threads:[~2001-08-21 5:57 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 ` David Pirotte [this message]
2001-08-20 22:36 ` gnome-guile-0.21pre2 Ariel Rios
2001-08-21 2:47 ` gnome-guile-0.21pre2 David Pirotte
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=3B824F6C.417AE0FF@altosw.be \
--to=david@altosw.be \
--cc=ariel@gnu.org \
--cc=ariel@linuxppc.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).