public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Michael Livshin <mlivshin@bigfoot.com>
To: Dave Cottingham <dc@cobi.gsfc.nasa.gov>
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: can't build it
Date: Fri, 01 Sep 2000 18:16:00 -0000	[thread overview]
Message-ID: <s3d7in1tvm.fsf@bigfoot.com> (raw)
In-Reply-To: <200009012137.RAA28119@cobi.gsfc.nasa.gov>

Dave Cottingham <dc@cobi.gsfc.nasa.gov> writes:

> I'm trying to build guile-gtk-0.19, and the make dies with:
> 
> gcc -g -O2 -o .libs/guile-gtk-1.2 main.o .libs/libguilegtk-1.2.so -L/usr/lib -L/usr/X11R6/lib -lgtk -lgdk -lgmodule -lglib -ldl -lXext -lX11 -lm -lm -L/usr/local/lib -lguile -lm -L/usr/lib -L/usr/X11R6/lib -lgtk -lgdk -rdynamic -lgmodule -lglib -ldl -lXext -lX11 -lm -lm -Wl,--export-dynamic -Wl,--rpath -Wl,/usr/local/lib
> .libs/libguilegtk-1.2.so: undefined reference to `scm_master_freelist'

this looks like your Guile libs and includes are of different versions 
(i.e. your includes are obviously 1.4 but your libs are 1.3.4 or
something).  so please check whether you disposed of the old Guile
libs properly.

[ note: I'm a Debian user, so I may well be wrong wrt your system. ]

> /usr/lib/libguile.so: undefined reference to `qt_abort'
> /usr/lib/libguile.so: undefined reference to `qt_error'
> /usr/lib/libguile.so: undefined reference to `qt_block'

probably related to the above.

let's see if I can be helpful when drunk,
--mike

-- 
For those who like this sort of thing, this is the sort of thing they like.
                                                                 -- fortune

      reply	other threads:[~2000-09-01 18:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-01 14:37 Dave Cottingham
2000-09-01 18:16 ` Michael Livshin [this message]

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=s3d7in1tvm.fsf@bigfoot.com \
    --to=mlivshin@bigfoot.com \
    --cc=dc@cobi.gsfc.nasa.gov \
    --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).