public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: rm@fabula.de
To: "Neil W. Van Dyke" <nwv@neilvandyke.org>
Cc: guile-gtk@sourceware.cygnus.com, guile-user@gnu.org, guile-devel@gnu.org
Subject: Taming the beast [was: Re: guile-gobject 0.3.0 Released]
Date: Wed, 06 Feb 2002 05:24:00 -0000	[thread overview]
Message-ID: <20020206133521.GA3525@www> (raw)
In-Reply-To: <15455.2102.116139.730545@winona.neilvandyke.org>

On Mon, Feb 04, 2002 at 05:16:22PM -0500, Neil W. Van Dyke wrote:
 
> In case anyone else has trouble building guile-gobject 0.3.0, here's the
> minor changes I needed.  Haven't actually run it, but it compiled.
> 
> 1. File "gobject/guile-gnome-gobject-primitives.c": Renamed identifiers
>    beginning with "g_param_get_" to begin with "g_param_spec_get_", per
>    http://mail.gnome.org/archives/gnome-2-0-list/2001-November/msg00121.html
> 
> 2. File "corba/Makefile.in": Added "$(GUILE_CFLAGS)" to "INCLUDES".
> 
> 3. File "corba/guile-gnome-corba-types.c": Temporarily added explicit cast to
>    get it to compile:   g_message (G_STRLOC ": %d", (int)gtype);
> 
> 4. Dependency on "libxml2" devel library does not seem to be checked by
>    configure script.  Other libraries might also need checking; this one 
>    noticed only because this particular box happened to be missing that
>    library.

Thanks for this info, it saved some time. Even after applying your 
changes i couldn't compile guile-gobject with my CVS guile . 
It seems that the code uses some deprecated/removed features. To get
a more or less error free compile i had to do the following:

 - change type 'scm_bits_t' to 'scm_t_bits' (see file NEWS in guile-core).

 - change 'LIST1, LIST2 ... LISTN' to 'scm_list_1 ... scm_list_n'
   (again, see file NEWS in guile-core).

 

With these modifications i can at least compile the shared library part.
Now, during 'make' i get the following errror:

|  make[2]: Entering directory `/home/ralf/projects/guile-gobject-0.3.0/gobject'
|  FLAVOR=gnome guile -c \
|  "(set! %load-path (cons \"..\" %load-path)) \
|   (primitive-load \"./gnome-gobject.gwp\")"
|  ERROR: Unbound variable: nil
|  make[2]: *** [gnomegobject.h] Error 2
|  make[2]: Leaving directory `/home/ralf/projects/guile-gobject-0.3.0/gobject'
|  make[1]: *** [all-recursive] Error 1
|  make[1]: Leaving directory `/home/ralf/projects/guile-gobject-0.3.0'
|  make: *** [all-recursive-am] Error 2
|  
 
Hmm,  no idea where 'nil' is supposed to come from. 
A quick grep didn't reveal anything. Ariel, any hints?

 Ralf Mattes

  reply	other threads:[~2002-02-06 13:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-28 11:29 guile-gobject 0.3.0 Released Ariel Rios
2002-01-29 19:01 ` Eric Gillespie
2002-01-29 20:39   ` Ariel Rios
2002-02-04 15:05     ` (Was: guile-gobject 0.3.0 Released) Neil W. Van Dyke
2002-02-04 21:30       ` Ariel Rios
2002-02-04 14:15 ` guile-gobject 0.3.0 Released Neil W. Van Dyke
2002-02-06  5:24   ` rm [this message]
2002-02-08  3:03     ` Taming the beast [was: Re: guile-gobject 0.3.0 Released] Neil Jerram

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=20020206133521.GA3525@www \
    --to=rm@fabula.de \
    --cc=guile-devel@gnu.org \
    --cc=guile-gtk@sourceware.cygnus.com \
    --cc=guile-user@gnu.org \
    --cc=nwv@neilvandyke.org \
    /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).