Am Mon, 20 Oct 2008 16:59:34 +0200 schrieb Johannes Hofmann <Johannes.Hofmann@gmx.de>:
With these options I can reproduce the problem. I guess --enable-cairo is the problematic one. Can you try to compile dillo with a manually compiled fltk2 without --enable-cairo?
Nothing easier than that with the source-based distro;-) I have a system fltk2 lib now without cairo and now dillo2 works nicely! So cairo in FLTK2 is buggy? Or its usage in dillo... but I suppose that FLTK2 should abstract that away. This could meant that we can close the bug; but the information about the cairo issue should be FAQed somewhere -- ideally, of course, solved upstream. Btw: FLTK2 not having a stable release is a bit of a problem with replacing the old "stable" dillo with dillo2... I hope that situation is resolved soon. Well, and the missing feature of frames; whatever one's opinion, the dillo patch that enabled this is commonplace and this missing is a de facto regression... But I'm really delighted to see that dillo is still alive, really. I dream of a lean, stable browser that can do https and CSS. Perhaps that dream comes true, finally. Alrighty then, Thomas.