public inbox for
 help / color / mirror / Atom feed
From: Stanislas Pinte <>
Subject: problem compiling guile-gtk-1.2-0.31
Date: Mon, 30 Sep 2002 10:10:00 -0000	[thread overview]
Message-ID: <> (raw)


I am trying to compile guile-gtk-1.2-0.31 with guile-1.6, and it fails 

I have got the impression of having gtk-1.2, which should be allright...

thanks for any help, here enclosed the first errors...

source='guile-gtk.c' object='guile-gtk.lo' libtool=yes \
depfile='.deps/guile-gtk.Plo' tmpdepfile='.deps/guile-gtk.TPlo' \
depmode=gcc /bin/sh ./depcomp \
/bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I. -I. -I. 
-I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include 
-D_REENTRANT -I/usr/X11R6/include -I/usr/local/include 
-I/usr/local/include   -g -O2 -c -o guile-gtk.lo `test -f 'guile-gtk.c' 
|| echo './'`guile-gtk.c
mkdir .libs
gcc -DHAVE_CONFIG_H -I. -I. -I. -I. -I. -I/usr/include/gtk-1.2 
-I/usr/include/glib-1.2 -I/usr/lib/glib/include -D_REENTRANT 
-I/usr/X11R6/include -I/usr/local/include -I/usr/local/include -g -O2 -c 
guile-gtk.c -Wp,-MD,.deps/guile-gtk.TPlo  -fPIC -DPIC -o .libs/guile-gtk.lo
In file included from /usr/include/stdio.h:33,
                  from guile-gtk.c:18,
                  from guile-gtk.c:2621:
/usr/lib/gcc-lib/i486-suse-linux/2.95.3/include/stddef.h: In function 
/usr/lib/gcc-lib/i486-suse-linux/2.95.3/include/stddef.h:170: parse 
error before `typedef'
In file included from /usr/include/stdio.h:35,
                  from guile-gtk.c:18,
                  from guile-gtk.c:2621:
/usr/include/bits/types.h: At top level:
/usr/include/bits/types.h:78: warning: empty declaration
/usr/include/bits/types.h:81: warning: redefinition of `__daddr_t'
/usr/include/bits/types.h:81: warning: `__daddr_t' previously declared here
/usr/include/bits/types.h:82: warning: redefinition of `__caddr_t'

                 reply	other threads:[~2002-09-30 17:10 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).