- Dillo-dev - lists.mailman3.com

Re: [fltk.general] Cross-compiling Dillo to ARM

by darirf＠yahoo.es

Hi Alan, A fellow user of the irex iliad tried to compile dillo2 for it (PXA255) and had similar issues with fltk2 (it was http://www.mobileread.com/forums/showpost.php?p=301183&postcount=84 ). Would you mind posting the configure flags that you have used for kdrive, fltk2 and dillo2? Thanks a lot. Hope that those configure also works for the iliad and we can replace the aging dillo 0.8.6 O:). Best regards and thanks again to all involved in dillo development. Dario. --- El mi?, 8/7/09, Alan Carvalho de Assis <acassis(a)gmail.com> escribi?: > De: Alan Carvalho de Assis <acassis(a)gmail.com> > Asunto: [Dillo-dev] Re: [fltk.general] Cross-compiling Dillo to ARM > Para: "Mirror of fltk.general Newsgroup" <fltk(a)easysw.com> > CC: "dillo-dev" <dillo-dev(a)dillo.org> > Fecha: mi?rcoles, 8 julio, 2009 8:58 > Hi Ian, > > On 7/8/09, imacarthur <imacarthur(a)gmail.com> > wrote: > > > > On 8 Jul 2009, at 16:33, Alan Carvalho de Assis > wrote: > > > > fltk-2 is not my strong suit, so what follows is just > guesswork > > really. However, here are some questions that might be > relevant: > > > > What fonts does your target system actually have > installed? Which > > names, what types, etc.? > > > > Now, the reason I ask is that I see from the gdb trace > that your > > program crashed in Font_xlfd.cxx, so presumably it was > attempting to > > load an "old style" XLFD font. > > > > You say your test build works with fltk-1.3, and it > defaults to using > > "new-style" XFT fonts, rather than using XLFD fonts > (although it can > > also use XLFD fonts, *or* can be built to only use > XLFD fonts by > > passing --disable-xft to configure at build time.) > > > > So... I'm guessing that the fltk-1.3 build works for > some reason > > because it is using XFT and the fltk-2 build fails > because it > > attempts to use XLFD. Does that seem feasible? > > > > If so, it might be worth trying to make sure the > fltk-2 build loads > > an XFT rather than XLFD font, see how that goes. > > > > All that said, however, a default flrk-2 build *ought* > to default to > > XFT enabled anyway - unless someone has changed that? > > > > Did you later that setting during config by any > chance? Maybe that is > > somewhere to start looking, if nothing else... > > > > You are right, I compiled Xorg (kdrive) with > "--enable-builtin-fonts", > then FLTK2 doesn't work. > > I think FLTK2 could to work with only "fixed" font, just > like FLTK1 does. > > Thank you very much! > > Regards, > > P.S.: Dillo is working fine on i.MX27 now! > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

July 9, 2009

(no subject)

by newman.x＠gmail.com

On Thu, Jul 9, 2009 at 9:20 AM, Michal Nowak<newman.x(a)gmail.com> wrote: > On Wed, Jul 8, 2009 at 5:33 PM, Alan Carvalho de Assis<acassis(a)gmail.com> wrote: >> Hi All, >> >> I am trying to port Dillo to i.MX27 (ARM9) processor. >> Using LTIB build system (www.ltib.org) to cross-compile FLTK. >> >> I cross-compiled FLTK2, but it is crashing, I can't run any demo example. >> >> To FLTK1.3 everything works fine, I ran all examples successfully. >> >> To FLTK2 nothing works. I searched Internet for similar error, but >> nothing solves it. >> >> I tested these FLTK revision: >> fltk-2.0.x-r6793 >> fltk-2.0.x-r6101 >> >> It appears to crash at "fltk::setfont". In fact I can see "bad font: >> fixed" message just before that "Segmentation Fault". >> >> Could someone give me some suggestion to solve this issue? >> >> See below the gdb backtrace. >> I am running gdbserver on i.MX27 board (IP 192.168.0.180) >> >> Best Regards, >> >> Alan >> >> $ arm-elf-gdb /home/alan/ltib/rootfs/home/test/hello >> GNU gdb 6.6 >> Copyright (C) 2006 Free Software Foundation, Inc. >> GDB is free software, covered by the GNU General Public License, and you are >> welcome to change it and/or distribute copies of it under certain conditions. >> Type "show copying" to see the conditions. >> There is absolutely no warranty for GDB. ?Type "show warranty" for details. >> This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-linux"... >> (gdb) target remote 192.168.0.180:3333 >> Remote debugging using 192.168.0.180:3333 >> warning: Unable to find dynamic linker breakpoint function. >> GDB will be unable to debug shared library initializers >> and track explicitly loaded dynamic code. >> 0x400007e0 in ?? () >> (gdb) set solib-absolute-prefix /home/alan/ltib/rootfs >> (gdb) b main >> Breakpoint 1 at 0xb9e8: file hello.cxx, line 9. >> (gdb) c >> Continuing. >> >> Breakpoint 1, main (argc=1, argv=0xbeaa5e44) at hello.cxx:9 >> 9 ? ? ? ? Window *window = new Window(300, 180); >> (gdb) c >> Continuing. >> >> Program received signal SIGSEGV, Segmentation fault. >> 0x4025dfe0 in strcmp () from /home/alan/ltib/rootfs/lib/libc.so.6 >> (gdb) bt >> #0 ?0x4025dfe0 in strcmp () from /home/alan/ltib/rootfs/lib/libc.so.6 >> #1 ?0x0000d1e4 in fltk::setfont (font=0x3a0ac, psize=12) at >> x11/Font_xlfd.cxx:542 >> #2 ?0x0001ac80 in fltk::Widget::draw_box (this=0x40b68, r=@0xbeaa5a18) >> at Widget_draw.cxx:94 >> #3 ?0x0001acc0 in fltk::Widget::draw_box (this=0x0) at Widget_draw.cxx:88 >> #4 ?0x0001a810 in fltk::Widget::draw (this=0x0) at Widget.cxx:644 >> #5 ?0x0000d618 in fltk::Group::draw_child (this=<value optimized out>, >> w=@0x40b68) >> ? ?at Group.cxx:750 >> #6 ?0x0000e218 in fltk::Group::draw (this=0x406e0) at Group.cxx:682 >> #7 ?0x00013ff8 in fltk::Window::flush (this=0x406e0) at x11/run.cxx:2566 >> #8 ?0x000116d4 in fl_window_flush (window=0x406e0) at run.cxx:657 >> #9 ?0x00011784 in fltk::flush () at run.cxx:691 >> #10 0x00016a60 in fltk::wait (time_to_wait=1.00000002e+20) at run.cxx:484 >> #11 0x00016b8c in fltk::run () at run.cxx:397 >> #12 0x402071cc in __libc_start_main () from /home/alan/ltib/rootfs/lib/libc.so.6 >> #13 0x0000b94c in _start () >> (gdb) >> >> _______________________________________________ >> Dillo-dev mailing list >> Dillo-dev(a)dillo.org >> http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >> > > I'd probably encourage you to file a FLTK2 bug upstream or send > an email to FLTK mailing list, however w.r.t FLTK2 I don't think they > will fix it soon anyway. My POV is that they answer to bug reports > but not fixing much. > > Michal > Too late :).

July 9, 2009

(no subject)

by newman.x＠gmail.com

On Wed, Jul 8, 2009 at 5:33 PM, Alan Carvalho de Assis<acassis(a)gmail.com> wrote: > Hi All, > > I am trying to port Dillo to i.MX27 (ARM9) processor. > Using LTIB build system (www.ltib.org) to cross-compile FLTK. > > I cross-compiled FLTK2, but it is crashing, I can't run any demo example. > > To FLTK1.3 everything works fine, I ran all examples successfully. > > To FLTK2 nothing works. I searched Internet for similar error, but > nothing solves it. > > I tested these FLTK revision: > fltk-2.0.x-r6793 > fltk-2.0.x-r6101 > > It appears to crash at "fltk::setfont". In fact I can see "bad font: > fixed" message just before that "Segmentation Fault". > > Could someone give me some suggestion to solve this issue? > > See below the gdb backtrace. > I am running gdbserver on i.MX27 board (IP 192.168.0.180) > > Best Regards, > > Alan > > $ arm-elf-gdb /home/alan/ltib/rootfs/home/test/hello > GNU gdb 6.6 > Copyright (C) 2006 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. ?Type "show warranty" for details. > This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-linux"... > (gdb) target remote 192.168.0.180:3333 > Remote debugging using 192.168.0.180:3333 > warning: Unable to find dynamic linker breakpoint function. > GDB will be unable to debug shared library initializers > and track explicitly loaded dynamic code. > 0x400007e0 in ?? () > (gdb) set solib-absolute-prefix /home/alan/ltib/rootfs > (gdb) b main > Breakpoint 1 at 0xb9e8: file hello.cxx, line 9. > (gdb) c > Continuing. > > Breakpoint 1, main (argc=1, argv=0xbeaa5e44) at hello.cxx:9 > 9 ? ? ? ? Window *window = new Window(300, 180); > (gdb) c > Continuing. > > Program received signal SIGSEGV, Segmentation fault. > 0x4025dfe0 in strcmp () from /home/alan/ltib/rootfs/lib/libc.so.6 > (gdb) bt > #0 ?0x4025dfe0 in strcmp () from /home/alan/ltib/rootfs/lib/libc.so.6 > #1 ?0x0000d1e4 in fltk::setfont (font=0x3a0ac, psize=12) at > x11/Font_xlfd.cxx:542 > #2 ?0x0001ac80 in fltk::Widget::draw_box (this=0x40b68, r=@0xbeaa5a18) > at Widget_draw.cxx:94 > #3 ?0x0001acc0 in fltk::Widget::draw_box (this=0x0) at Widget_draw.cxx:88 > #4 ?0x0001a810 in fltk::Widget::draw (this=0x0) at Widget.cxx:644 > #5 ?0x0000d618 in fltk::Group::draw_child (this=<value optimized out>, > w=@0x40b68) > ? ?at Group.cxx:750 > #6 ?0x0000e218 in fltk::Group::draw (this=0x406e0) at Group.cxx:682 > #7 ?0x00013ff8 in fltk::Window::flush (this=0x406e0) at x11/run.cxx:2566 > #8 ?0x000116d4 in fl_window_flush (window=0x406e0) at run.cxx:657 > #9 ?0x00011784 in fltk::flush () at run.cxx:691 > #10 0x00016a60 in fltk::wait (time_to_wait=1.00000002e+20) at run.cxx:484 > #11 0x00016b8c in fltk::run () at run.cxx:397 > #12 0x402071cc in __libc_start_main () from /home/alan/ltib/rootfs/lib/libc.so.6 > #13 0x0000b94c in _start () > (gdb) > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev > I'd probably encourage you to file a FLTK2 bug upstream or send an email to FLTK mailing list, however w.r.t FLTK2 I don't think they will fix it soon anyway. My POV is that they answer to bug reports but not fixing much. Michal

July 9, 2009

Re: [fltk.general] Cross-compiling Dillo to ARM

by acassis＠gmail.com

Hi Ian, On 7/8/09, imacarthur <imacarthur(a)gmail.com> wrote: > > On 8 Jul 2009, at 16:33, Alan Carvalho de Assis wrote: > > fltk-2 is not my strong suit, so what follows is just guesswork > really. However, here are some questions that might be relevant: > > What fonts does your target system actually have installed? Which > names, what types, etc.? > > Now, the reason I ask is that I see from the gdb trace that your > program crashed in Font_xlfd.cxx, so presumably it was attempting to > load an "old style" XLFD font. > > You say your test build works with fltk-1.3, and it defaults to using > "new-style" XFT fonts, rather than using XLFD fonts (although it can > also use XLFD fonts, *or* can be built to only use XLFD fonts by > passing --disable-xft to configure at build time.) > > So... I'm guessing that the fltk-1.3 build works for some reason > because it is using XFT and the fltk-2 build fails because it > attempts to use XLFD. Does that seem feasible? > > If so, it might be worth trying to make sure the fltk-2 build loads > an XFT rather than XLFD font, see how that goes. > > All that said, however, a default flrk-2 build *ought* to default to > XFT enabled anyway - unless someone has changed that? > > Did you later that setting during config by any chance? Maybe that is > somewhere to start looking, if nothing else... > You are right, I compiled Xorg (kdrive) with "--enable-builtin-fonts", then FLTK2 doesn't work. I think FLTK2 could to work with only "fixed" font, just like FLTK1 does. Thank you very much! Regards, P.S.: Dillo is working fine on i.MX27 now!

July 8, 2009

(no subject)

by acassis＠gmail.com

Hi All, I am trying to port Dillo to i.MX27 (ARM9) processor. Using LTIB build system (www.ltib.org) to cross-compile FLTK. I cross-compiled FLTK2, but it is crashing, I can't run any demo example. To FLTK1.3 everything works fine, I ran all examples successfully. To FLTK2 nothing works. I searched Internet for similar error, but nothing solves it. I tested these FLTK revision: fltk-2.0.x-r6793 fltk-2.0.x-r6101 It appears to crash at "fltk::setfont". In fact I can see "bad font: fixed" message just before that "Segmentation Fault". Could someone give me some suggestion to solve this issue? See below the gdb backtrace. I am running gdbserver on i.MX27 board (IP 192.168.0.180) Best Regards, Alan $ arm-elf-gdb /home/alan/ltib/rootfs/home/test/hello GNU gdb 6.6 Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-linux"... (gdb) target remote 192.168.0.180:3333 Remote debugging using 192.168.0.180:3333 warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. 0x400007e0 in ?? () (gdb) set solib-absolute-prefix /home/alan/ltib/rootfs (gdb) b main Breakpoint 1 at 0xb9e8: file hello.cxx, line 9. (gdb) c Continuing. Breakpoint 1, main (argc=1, argv=0xbeaa5e44) at hello.cxx:9 9 Window *window = new Window(300, 180); (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x4025dfe0 in strcmp () from /home/alan/ltib/rootfs/lib/libc.so.6 (gdb) bt #0 0x4025dfe0 in strcmp () from /home/alan/ltib/rootfs/lib/libc.so.6 #1 0x0000d1e4 in fltk::setfont (font=0x3a0ac, psize=12) at x11/Font_xlfd.cxx:542 #2 0x0001ac80 in fltk::Widget::draw_box (this=0x40b68, r=@0xbeaa5a18) at Widget_draw.cxx:94 #3 0x0001acc0 in fltk::Widget::draw_box (this=0x0) at Widget_draw.cxx:88 #4 0x0001a810 in fltk::Widget::draw (this=0x0) at Widget.cxx:644 #5 0x0000d618 in fltk::Group::draw_child (this=<value optimized out>, w=@0x40b68) at Group.cxx:750 #6 0x0000e218 in fltk::Group::draw (this=0x406e0) at Group.cxx:682 #7 0x00013ff8 in fltk::Window::flush (this=0x406e0) at x11/run.cxx:2566 #8 0x000116d4 in fl_window_flush (window=0x406e0) at run.cxx:657 #9 0x00011784 in fltk::flush () at run.cxx:691 #10 0x00016a60 in fltk::wait (time_to_wait=1.00000002e+20) at run.cxx:484 #11 0x00016b8c in fltk::run () at run.cxx:397 #12 0x402071cc in __libc_start_main () from /home/alan/ltib/rootfs/lib/libc.so.6 #13 0x0000b94c in _start () (gdb)

July 8, 2009

.deb files as PPA

by sas＠321.hu

Hello, On Tue, Jul 7, 2009 at 7:24 PM, Jorge Arellano Cid <jcid(a)dillo.org> wrote: > Hi, > > Now that launchpad is back, .deb packages for Debian on squeeze: dillo depends on libxi6 (>= 2:1.2.0); however: Version of libxi6 on system is 2:1.1.4-1. -- SZERV?C Attila http://321.hu/sas SALVI N?ra http://321.hu/zene.html

July 7, 2009

.deb files as PPA

by jcid＠dillo.org

Hi, Now that launchpad is back, .deb packages for Debian and Ubuntu are available from our download page. -- Cheers Jorge.-

July 7, 2009

client-side redirect

by corvid＠lavabit.com

I went to http://home.williampoundstone.net/Keeler/ and it breaks because there's a space before the URL in <meta http-equiv="refresh" content="0;url= Home.html" /> I can't seem to find anything that does a careful job of specifying what's legal here.

July 5, 2009

dillo-2.1.1 released

by kelson＠pobox.com

On Friday 03 July 2009, Jorge Arellano Cid wrote: > Alexander, > > On Fri, Jul 03, 2009 at 10:15:19PM +0200, Alexander Voigt wrote: > > Dear Dillo developers, > > > > could please anyone be so kind and build an Debian/Ubuntu package for > > the new Dillo 2.1.1? > > Our packagers are aware and working on it. Unfortunately > we're a bit behind the announcement. Packages should be ready in > a day or two (I updated the download page saying it so). > > Sorry for the inconvenience. Sorry for the delay -- it's a holiday weekend here. I've posted Fedora 10 i386 and RHEL5 i386 & x86_64, both SSL and non-SSL, at http://www.hyperborea.org/software/dillo/ -- Kelson Vibber www.hyperborea.org and SpeedForce.org

July 5, 2009

dillo 2.1]

by xentalion＠gmail.com

> Does anyone know what the contemporary way is to show the information > in Plans.html? I remember ball.gif being ubiquitous in html in 1995 -- > in stratigraphy it is regarded as a valuable 'index fossil', often found > together with a variety of brightly-colored line.gifs and blink tags -- > but I don't know what to do about it. > For the Plans.html, I'd use a list with each item having a background image from a sprite sheet ala http://www.alistapart.com/articles/sprites/, but that requires background image support in Dillo. In the mean time, maybe change the icons to pngs of check marks and Xs or something. Maybe green Xs for unfinished features and red Xs for pending? When I first saw the new website, I was surprised, but I have to say that I like it. On Wed, Jun 24, 2009 at 5:53 PM, Jorge Arellano Cid <jcid(a)dillo.org> wrote: > On Wed, Jun 24, 2009 at 06:59:00PM +0000, corvid wrote: > > Jorge wrote: > > > On Tue, Jun 23, 2009 at 11:05:07PM +0000, corvid wrote: > > > > Jorge wrote: > > > > > On Mon, Jun 22, 2009 at 11:01:12PM +0300, Tomas Rimkus wrote: > > > > > > > > > > > > Accidentally sent to corvid only. Forwarding to dillo-dev. > > > > > > > > > > > > > > > It seems whoever designed the new website theme has no idea > what > > > > > > > > > READABILITY means... It looks like someone just used some > stupid online > > > > > > > > > color picker, which just picks some similar colors to the > one user > > > > > > > > > chooses. The old website looked MUCH MUCH better. Imho, > it's a > > > > > > > > > regression... > > > > > > > > > > > > > > > > Hm I like the new design, but I agree that readability might > be a problem. > > > > > > > > Let's see what other say. > > > > > > > > > > > > > > I still find visited text to be hard to read, but I know I > should > > > > > > > break down and get a new display... > > > > > > > > > > > > > > > > > > > I wonder if you are the only dillo user with old display... BTW, > I am using > > > > > > pretty new LCD display and still find it hard to read. > > > > > > > > > > OK, we also had readability concerns but we agreed that it was > > > > > enough. OTOH some people bashed the old design as prehistoric! > > > > > > > > > > After all it's a matter of taste. > > > > > Usability is a different thing. Maybe you need higher contrast > > > > > to see clearly (I suffer with white backgrounds). Do you find > > > > > this one better to read [1]? > > > > > > > > > > What do other people think about the new web design? > > > > > Aesthetically and from a readability point of view. > > > > > Please comment. > > > > > > > > > > > > > > > [1] http://www.dillo.org/test/website/dillo2.2.html > > > > > > > > The test page's visited text is easier for me to read than > > > > the home page's visited text. > > > > > > Funny how it's the reverse effect for me! :-) > > > > > > > > > Please test: > > > > > > :visited {color: #403090 !important} > > > > > > and > > > > > > :visited {color: #603060 !important} > > > > > > on http://www.dillo.org/ and FAQ. > > > > > > I prefer the first one because it fits the palette better. > > > > First one is easier. > > Committed. > > -- > Cheers > Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

July 4, 2009