- Dillo-dev - lists.mailman3.com

what's currently broken in dillo

by jcid＠dillo.org

On Mon, Nov 17, 2014 at 01:54:46PM -0300, Jorge Arellano Cid wrote: > Hi, > > On Sun, Nov 16, 2014 at 05:17:06AM +0000, eocene wrote: > > Jeremy wrote: > > > The Dillo source does something a little devious. It refers to > > > fl_oldfocus, but this symbol is not declared in any header, it is just > > > shared between two *.c files via an extern declaration (with a comment > > > that this is a hack to make Fl_Group work). Something has changed in > > > libfltk.so to stop the linker finding this symbol. I don't know what > > > (I am not experienced in debugging linking failures.) > > > > To the best of my recollection, something tricky was necessary because > > Fl_Group didn't have the idea that the group itself could have focus > > instead of one of the children. I can't immediately see how to get it > > to work right without fl_oldfocus, but if we can't link, we have nothing, > > so I'll take out fl_oldfocus, and hopefully someone will figure out > > something at some point... > > Good try, wandering focus got so annoying that I had to start scratching > the itch! ;) > > FYI, I'm testing a patch that so far behaves OK. Committed. -- Cheers Jorge.-

Nov. 18, 2014

what's currently broken in dillo

by onepoint＠starurchin.org

Jorge Arellano Cid wrote: > On Mon, Nov 17, 2014 at 05:33:41PM +0000, Jeremy Henty wrote: > > > > Should we release 3.0.5 to fix this for distro users? Otherwise their > > dillo will break when their distro updates to a FLTK-1.3.3 *.so . > > IMHO current repo is not as stable as it should for a new release. > > I'd pack a 3.0.4.1 with the fix for FLTK-1.3.3. That was what I had in mind. Sorry if that was not clear. > The repo has more than enough for a version bump when its moment > comes! I would say it deserves to be 3.1 at least! :-) Regards, Jeremy Henty

Nov. 17, 2014

what's currently broken in dillo

by jcid＠dillo.org

Hi Jeremy, On Mon, Nov 17, 2014 at 05:33:41PM +0000, Jeremy Henty wrote: > > eocene wrote: > > > [...] I'll take out fl_oldfocus, and hopefully someone will figure > > out something at some point... > > Should we release 3.0.5 to fix this for distro users? Otherwise their > dillo will break when their distro updates to a FLTK-1.3.3 *.so . IMHO current repo is not as stable as it should for a new release. I'd pack a 3.0.4.1 with the fix for FLTK-1.3.3. The repo has more than enough for a version bump when its moment comes! -- Cheers Jorge.-

Nov. 17, 2014

what's currently broken in dillo

by onepoint＠starurchin.org

eocene wrote: > [...] I'll take out fl_oldfocus, and hopefully someone will figure > out something at some point... Should we release 3.0.5 to fix this for distro users? Otherwise their dillo will break when their distro updates to a FLTK-1.3.3 *.so . Regards, Jeremy Henty

Nov. 17, 2014

what's currently broken in dillo

by jcid＠dillo.org

Hi, On Sun, Nov 16, 2014 at 05:17:06AM +0000, eocene wrote: > Jeremy wrote: > > The Dillo source does something a little devious. It refers to > > fl_oldfocus, but this symbol is not declared in any header, it is just > > shared between two *.c files via an extern declaration (with a comment > > that this is a hack to make Fl_Group work). Something has changed in > > libfltk.so to stop the linker finding this symbol. I don't know what > > (I am not experienced in debugging linking failures.) > > To the best of my recollection, something tricky was necessary because > Fl_Group didn't have the idea that the group itself could have focus > instead of one of the children. I can't immediately see how to get it > to work right without fl_oldfocus, but if we can't link, we have nothing, > so I'll take out fl_oldfocus, and hopefully someone will figure out > something at some point... Good try, wandering focus got so annoying that I had to start scratching the itch! ;) FYI, I'm testing a patch that so far behaves OK. -- Cheers Jorge.-

Nov. 17, 2014

What's the repository for latest dillo?

by Johannes.Hofmann＠gmx.de

Hi Walter, On Mon, Nov 17, 2014 at 12:31:46AM -0500, Walter Dnes wrote: > I've got dillo-3.0.4 running on Gentoo linux, with fltk-1.3.2. People > here seem to be running experimental "bleeding edge" versions. I assume > it's from a git repo. What are the instructions to download and build > dillo, preferably in my user directory? I'm aware that it may be broken > on edge cases. > > I'm not a C programmer. My main skills are in bash shell scripting. > If nothing else, I'll be another tester. instructions how to get the latest sources can be found at http://www.dillo.org/source.html Cheers, Johannes

Nov. 17, 2014

What's the repository for latest dillo?

by waltdnes＠waltdnes.org

I've got dillo-3.0.4 running on Gentoo linux, with fltk-1.3.2. People here seem to be running experimental "bleeding edge" versions. I assume it's from a git repo. What are the instructions to download and build dillo, preferably in my user directory? I'm aware that it may be broken on edge cases. I'm not a C programmer. My main skills are in bash shell scripting. If nothing else, I'll be another tester. -- Walter Dnes <waltdnes at waltdnes.org>

Nov. 17, 2014

what's currently broken in dillo

by onepoint＠starurchin.org

I wrote: > The Dillo source does something a little devious. It refers to > fl_oldfocus, but this symbol is not declared in any header, it is > just shared between two *.c files via an extern declaration (with a > comment that this is a hack to make Fl_Group work). Something has > changed in libfltk.so to stop the linker finding this symbol. I > don't know what (I am not experienced in debugging linking > failures.) Got it! When using autoconf, FLTK-1.3.3 compiles (if possible) with -fvisibility=hidden . This means that fl_oldfocus is marked as local instead of global in libfltk.so , which breaks linking Dillo. You can work around this with " ac_cv_cxx_fvisibility=no ./configure ... ". Regards, Jeremy Henty

Nov. 16, 2014

what's currently broken in dillo

by eocene＠gmx.com

Jeremy wrote: > The Dillo source does something a little devious. It refers to > fl_oldfocus, but this symbol is not declared in any header, it is just > shared between two *.c files via an extern declaration (with a comment > that this is a hack to make Fl_Group work). Something has changed in > libfltk.so to stop the linker finding this symbol. I don't know what > (I am not experienced in debugging linking failures.) To the best of my recollection, something tricky was necessary because Fl_Group didn't have the idea that the group itself could have focus instead of one of the children. I can't immediately see how to get it to work right without fl_oldfocus, but if we can't link, we have nothing, so I'll take out fl_oldfocus, and hopefully someone will figure out something at some point...

Nov. 16, 2014

what's currently broken in dillo

by onepoint＠starurchin.org

higuita wrote: > > > ../dw/libDw-fltk.a(libDw_fltk_a-fltkviewbase.o): In function > > > `dw::fltk::FltkViewBase::handle(int)': /home/higuita/build/dillo2/dillo3/dw/fltkviewbase.cc:367: > > > undefined reference to `fl_oldfocus' collect2: error: ld returned 1 > > > exit status make[3]: *** [dillo] Error 1 > > I'm not sure why you're getting that. > > I found that if i revert to fltk 1.3.2 it works, again building > the fltk 1.3.3, dillo build fails again. > > I have done make clean on fltk and dillo on every try and tried > to clean the system from any old files, but same results. > > greping the both fltk version for fl_oldfocus, i get the same > code, so is even weirder. > > Can someone reproduce this or i have something broken on my > system? I can reproduce this. The Dillo source does something a little devious. It refers to fl_oldfocus, but this symbol is not declared in any header, it is just shared between two *.c files via an extern declaration (with a comment that this is a hack to make Fl_Group work). Something has changed in libfltk.so to stop the linker finding this symbol. I don't know what (I am not experienced in debugging linking failures.) Incidentally, yoshimi also fails to link against FLTK-1.3.3, although a different symbol is involved. Regards, Jeremy Henty

Nov. 15, 2014