guile-gtk-general
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: how do you build this guile-gobject thing?


From: Andreas Rottmann
Subject: Re: how do you build this guile-gobject thing?
Date: Sat, 24 Jan 2004 13:41:26 +0100
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)

Matto Marjanovic <address@hidden> writes:

> Hiya,
>
> I'm trying to build/use v0.5.3 of guile-gobject.
>
> I've checked out the source tree from CVS, and I believe I've installed
>  all the dev packages needed to build it.  (I'm doing this on a Debian
>  unstable system.)  The only thing little niggle I can think of is a
>  message from ./configure:
>
>       *** Remember to update g-wrap as described in the README ***
>
That's a bit confusing: Are you using 0.5.3 or CVS? Both shouldn't
yield this message.

>  The README doesn't mention g-wrap at all.  The mailing lists show
>  evidence of some development activity in an Arch archive somewhere,
>  but I don't know how to access it or whether that is relevant.
>
See http://mail.gnu.org/archive/html/guile-gtk-general/2004-01/msg00036.html.

>  (I have "libgwrapguile-dev" installed, Debian version 1.3.4-11.)
>
> ./autogen.sh is happy.
> ./configure is happy.
> make is happy... until building libguile_gnome_gw_gtk_la-guile-gnome-gw-gtk.o.
>  Then, gcc grinds away, and eventually runs out of memory and quits.
>
> Any clues, suggestions?
>
Yes, compile with -O0. This is a known problem and already fixed my
modified version of g-wrap; my changes will go upstream RSN.

> (I'd settle for a .deb...)
>
I have already filed an ITP (see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=205465).

Cheers, Andy
-- 
Andreas Rottmann         | address@hidden      | address@hidden | address@hidden
http://yi.org/rotty      | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint              | DFB4 4EB4 78A4 5EEE 6219  F228 F92F CFC5 01FD 5B62

Any technology not indistinguishable from magic is insufficiently advanced.
   -- Terry Pratchett




reply via email to

[Prev in Thread] Current Thread [Next in Thread]