Re: [Chicken-users] IUP

[Thomas Chust]

Andy Bennett wrote:
> [...]
> ...there doesn't seem to be a libwebkit for Debian Wheezy: only a gtk
> version so I tried to disable all the web stuff in the iup.setup file.
> [...]

Hello Andy,

the GTK+ WebKit library is probably the right one unless you built IUP
against Motif instead of GTK+.

But you can also simply disable the WebKit binding by passing

  -feature disable-iup-web

to chicken-install.

> [...]
> Having done that and got a completed build I tried again:
> 
> -----
> #;1> (use iup)
> ; loading /usr/local/chicken-4.7.0/lib/chicken/6/iup.import.so ...
> ; loading /usr/local/chicken-4.7.0/lib/chicken/6/iup-base.import.so ...
> ; loading /usr/local/chicken-4.7.0/lib/chicken/6/lolevel.import.so ...
> ; loading /usr/local/chicken-4.7.0/lib/chicken/6/srfi-42.import.so ...
> ; loading /usr/local/chicken-4.7.0/lib/chicken/6/irregex.import.so ...
> ; loading /usr/local/chicken-4.7.0/lib/chicken/6/iup-controls.import.so ...
> ; loading /usr/local/chicken-4.7.0/lib/chicken/6/iup-dialogs.import.so ...
> ; loading /usr/local/chicken-4.7.0/lib/chicken/6/iup.so ...
> ; loading /usr/local/chicken-4.7.0/lib/chicken/6/srfi-42.so ...
> Segmentation fault
> -----
> [...]

Hmm, that probably means that initialization code of the IUP binding or
the IUP library itself is crashing since the SEGV apparently occurs at
some point after the SRFI-42 support library is loaded which is
triggered by a require-library call at the head of iup.scm.

However, without some information about the exact location of the crash
and your environment it's hard to say anything more than that :-(

You might try to disable more of the optional IUP modules using -feature
switches during the build and see whether that prevents triggering the bug.

Ciao,
Thomas


-- 
When C++ is your hammer, every problem looks like your thumb.