From: David Pirotte <david@altosw.be>
To: guile-devel <guile-devel@gnu.org>
Subject: guile-gnome - make check fails when compiled against gcc 5.2 - help needed
Date: Thu, 8 Oct 2015 19:59:55 -0300 [thread overview]
Message-ID: <20151008195955.0183c772@capac> (raw)
[-- Attachment #1: Type: text/plain, Size: 3153 bytes --]
Hello,
guile-gnome - any branch
make check fails when compiled against gcc 5.2
I'm looking for help from someone who knows well C in general and gcc in particular,
to debug the above shortly described situation:
note that both make and make check work fine with gcc 4.9.3 [and previous 4.x
versions as well]
In order to reproduce, you'll only need to install the development files for the
following wrappers:
glib-2.0
gobject-2.0
gthread-2.0 [ mandatory, scm_init_gnome_gobject_gc
[ calls g_thread_init
Then you need to install:
g-wrap [ from the source is optional
http://www.nongnu.org/g-wrap/developers.html
guile-cairo [ from the source is mandatory
http://www.nongnu.org/guile-cairo/dev/
guile-gnome [ from the source devel branch is preferred
[ since it would be to help me ...
https://www.gnu.org/software/guile-gnome/developers.html
git clone git://git.sv.gnu.org/guile-gnome.git
cd guile-gnome
git checkout devel
./autogen.sh
./configure [--prefix=/your/prefix]
make
make check
-> ...
;;;
compiling .../glib/gnome/gobject/gclosure.scm ;;;
compiled .../cache/ ... /glib/gnome/gobject/gclosure.scm.go ;;;
WARNING: compilation of.../glib/gnome/glib.scm
failed: ;;; ERROR: Throw to key `gruntime-error' with args
`("%gtype-class-bind" "No GType registered with name ~A" ("GClosure") ())'.
The reason glib/gnome/glib.scm fails is actually because it uses glib/gnome/gobject/gclosure.scm
which fails to define the <gclosure> class.
The best way to reproduce the error and start to track the problem down is, imo, by doing
this, from an emacs shell in the top-level guile-gnome source tree:
M-x run-guile
(set! %load-path (cons (string-append (getcwd) "/glib") %load-path))
,use (gnome gobject config)
,use (gnome gobject utils)
,use (gnome gobject gtype)
,use (gnome gobject gvalue)
,use (oop goops)
(define-class <gclosure> (<gboxed>) #:gtype-name "GClosure")
ERROR: In procedure %gtype-class-bind:
ERROR: Throw to key `gruntime-error' with args `("%gtype-class-bind" "No GType registered with name ~A" ("GClosure") ())'.
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
I see the file glib/gnome/gobject/gclosure.c, at the end of the file, defines:
static GType gcc_please_look_the_other_way;
void
scm_init_gnome_gobject_closures (void)
{
#ifndef SCM_MAGIC_SNARFER
#include "gclosure.x"
#endif
/* make sure the GClosure type is registered */
gcc_please_look_the_other_way = g_closure_get_type ();
}
but that is far as I've been till now. I don't know C well enough and this happens at a lower level then
my actual guile-gnome knowledge [still learning on both side...] I actually don't understand yet how this
gcc_please_look_the_other_way and scm_init_gnome_gobject_closures are 'triggered', neither this
SCM_MAGIC_SNARFER ...
Note that, once more, this bug does not happen when using gcc < 5.0
I would be really happy to receive some help,
Thanks,
David
For info, on debian, gclosure.h is here:
/usr/glib-2.0/gobject/gclosure.h
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
reply other threads:[~2015-10-08 22:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151008195955.0183c772@capac \
--to=david@altosw.be \
--cc=guile-devel@gnu.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).