- Dillo-dev - lists.mailman3.com

AW: [Dillo-dev] Crosscompiling Dillo2 for uClinux on Blackfin
by heisermi＠hs-albsig.de Aug. 15, 2009

Aug. 15, 2009

Hey guys, I think I'm near on getting dillo2 working on blackfin uClinux. My concurrent problem is, that there are some Errors linking the project. Undefined reference ..... I'll give you my compile log: make[3]: F?r das Ziel ?all? ist nichts zu tun. make[3]: Leaving directory `/home/mheiser/dillo-2.1.1/src/IO' make[3]: Entering directory `/home/mheiser/dillo-2.1.1/src' bfin-linux-uclibc-g++ -I.. -I/home/mheiser/uClinux/uClinux/uclinux-dist/staging/usr/include/libpng12 -I/home/mheiser/fltk-2.0.x-r6841 -I/home/mheiser/uClinux/uclinux-dist/staging/usr/include/freetype2 -I/home/mheiser/uClinux/uclinux-dist/user/microwin/nxlib/nxlib-0.45/X11/include -Wno-non-virtual-dtor -O2 -pipe -isystem /home/mheiser/uClinux/uclinux-dist/staging/usr/include -Wall -W -Wno-unused-parameter -fno-rtti -fno-exceptions -L/home/mheiser/uClinux/uclinux-dist/staging/usr/lib -o dillo dillo.o paths.o ui.o uicmd.o bw.o cookies.o auth.o colors.o misc.o history.o prefs.o prefsparser.o keys.o url.o bitvec.o klist.o chain.o utf8.o timeout.o dialog.o web.o nav.o cache.o decode.o dicache.o capi.o css.o cssparser.o styleengine.o plain.o html.o form.o table.o bookmark.o dns.o gif.o jpeg.o png.o imgbuf.o image.o menu.o dpiapi.o findbar.o xembed.o ../dlib/libDlib.a ../dpip/libDpip.a IO/libDiof.a ../dw/libDw-widgets.a ../dw/libDw-fltk.a ../dw/libDw-core.a ../lout/liblout.a -ljpeg -lpng12 -L/home/mheiser/fltk-2.0.x-r6841/lib -Wl,-rpath,/home/mheiser/bfin-fltk2/lib -lfltk2_images -lpng -lfltk2_images -ljpeg -lz -lfltk2 -L/home/mheiser/uClinux/uclinux-dist/user/microwin/nxlib/nxlib-0.45 -L/home/mheiser/uClinux/uclinux-dist/user/microwin/src/lib -L/home/mheiser/uClinux/uclinux-dist/staging/usr/lib -lX11 -lpthread -lm -lnano-X -lsupc++ -lz -liconv /home/mheiser/fltk-2.0.x-r6841/lib/libfltk2.so: undefined reference to `_Xutf8LookupString' /home/mheiser/fltk-2.0.x-r6841/lib/libfltk2.so: undefined reference to `_XFreeDeviceList' /home/mheiser/fltk-2.0.x-r6841/lib/libfltk2.so: undefined reference to `_wcstombs' /home/mheiser/fltk-2.0.x-r6841/lib/libfltk2.so: undefined reference to `_mbstowcs' /home/mheiser/fltk-2.0.x-r6841/lib/libfltk2.so: undefined reference to `_XOpenDevice' /home/mheiser/fltk-2.0.x-r6841/lib/libfltk2.so: undefined reference to `_XGetExtensionVersion' /home/mheiser/fltk-2.0.x-r6841/lib/libfltk2.so: undefined reference to `_XListInputDevices' /home/mheiser/fltk-2.0.x-r6841/lib/libfltk2.so: undefined reference to `_XSelectExtensionEvent' collect2: ld gab 1 als Ende-Status zur?ck make[3]: *** [dillo] Fehler 1 make[3]: Leaving directory `/home/mheiser/dillo-2.1.1/src' make[2]: *** [all-recursive] Fehler 1 make[2]: Leaving directory `/home/mheiser/dillo-2.1.1/src' make[1]: *** [all-recursive] Fehler 1 make[1]: Leaving directory `/home/mheiser/dillo-2.1.1' make: *** [all] Fehler 2 Can you give me an advice? I don't know exactly where I should begin searching for advice.... Regards Michael -----Urspr?ngliche Nachricht----- Von: corvid [mailto:corvid@lavabit.com] Gesendet: Donnerstag, 13. August 2009 02:10 An: Heiser Michael Betreff: Re: [Dillo-dev] Crosscompiling Dillo2 for uClinux on Blackfin If you get it working from that document mentioned on the uclinux forum, let us know so that I can add to Compatibility.html :) Von AVG ?berpr?ft - www.avg.de Version: 8.5.386 / Virendatenbank: 270.13.53/2299 - Ausgabedatum: 08/12/09 18:12:00

5 9

AW: [Dillo-dev] Crosscompiling Dillo2 for uClinux on Blackfin
by heisermi＠hs-albsig.de Aug. 14, 2009

Aug. 14, 2009

By the way, what I forgot to mention!! You have to change all fork() to vfork() cause there is no MMU on blackfin systems!!! Thanks Alan, it was a pleasure to me :) Regards Michael -----Urspr?ngliche Nachricht----- Von: Alan Carvalho de Assis [mailto:acassis@gmail.com] Gesendet: Freitag, 14. August 2009 16:02 An: Heiser Michael Betreff: Re: [Dillo-dev] Crosscompiling Dillo2 for uClinux on Blackfin Great work Michael, Thank you for sharing it. I hope someone implement these missing functions. NXLib is a nice project, I am sad to see this project stalled. Regards, Alan On 8/14/09, Heiser Michael <heisermi(a)hs-albsig.de> wrote: > Hey guys, > > I got it! Dillo2 is running on our Blackfin device and I'll send you a > little manual as attachment for implementing it to uClinux! > > Regards Michael!!! > > -----Urspr?ngliche Nachricht----- > Von: dillo-dev-bounces(a)dillo.org [mailto:dillo-dev-bounces@dillo.org] Im > Auftrag von Heiser Michael > Gesendet: Freitag, 14. August 2009 13:18 > An: dillo-devel-list (dillo-dev(a)dillo.org) > Betreff: AW: [Dillo-dev] Crosscompiling Dillo2 for uClinux on Blackfin > > LibXi is part of nxlib and nxlib maps XInputs to nano-X lib. So I had to > replace libXi. By the way I handled the compiling for Blackfin!! I will give > you soon an advice how to make it :) It's now only on testing dillo on our > device..... > > That seems to be tricky > > -----Urspr?ngliche Nachricht----- > Von: dillo-dev-bounces(a)dillo.org [mailto:dillo-dev-bounces@dillo.org] Im > Auftrag von Michal Nowak > Gesendet: Freitag, 14. August 2009 12:36 > An: dillo-dev(a)dillo.org > Betreff: Re: [Dillo-dev] Crosscompiling Dillo2 for uClinux on Blackfin > > On Fri, Aug 14, 2009 at 9:00 AM, Heiser Michael<heisermi(a)hs-albsig.de> > wrote: >> Hey guys, >> I think I'm near on getting dillo2 working on blackfin uClinux. My >> concurrent problem is, that there are some Errors linking the project. >> Undefined reference ..... >> I'll give you my compile log: >> >> make[3]: F?r das Ziel ?all? ist nichts zu tun. >> make[3]: Leaving directory `/home/mheiser/dillo-2.1.1/src/IO' >> make[3]: Entering directory `/home/mheiser/dillo-2.1.1/src' >> bfin-linux-uclibc-g++ -I.. >> bfin-linux-uclibc-g++ -I/home/mheiser/uClinux/uClinux/uclinux-dist/sta >> bfin-linux-uclibc-g++ ging/usr/include/libpng12 >> bfin-linux-uclibc-g++ -I/home/mheiser/fltk-2.0.x-r6841 >> bfin-linux-uclibc-g++ -I/home/mheiser/uClinux/uclinux-dist/staging/usr >> bfin-linux-uclibc-g++ /include/freetype2 >> bfin-linux-uclibc-g++ -I/home/mheiser/uClinux/uclinux-dist/user/microw >> bfin-linux-uclibc-g++ in/nxlib/nxlib-0.45/X11/include >> bfin-linux-uclibc-g++ -Wno-non-virtual-dtor -O2 -pipe -isystem >> bfin-linux-uclibc-g++ /home/mheiser/uClinux/uclinux-dist/staging/usr/i >> bfin-linux-uclibc-g++ nclude -Wall -W -Wno-unused-parameter -fno-rtti >> bfin-linux-uclibc-g++ -fno-exceptions >> bfin-linux-uclibc-g++ -L/home/mheiser/uClinux/uclinux-dist/staging/usr >> bfin-linux-uclibc-g++ /lib -o dillo dillo.o paths.o ui.o uicmd.o bw.o >> bfin-linux-uclibc-g++ cookies.o auth.o colors.o misc.o history.o >> bfin-linux-uclibc-g++ prefs.o prefsparser.o keys.o url.o bitvec.o >> bfin-linux-uclibc-g++ klist.o chain.o utf8.o timeout.o dialog.o web.o >> bfin-linux-uclibc-g++ nav.o cache.o decode.o dicache.o capi.o css.o >> bfin-linux-uclibc-g++ cssparser.o styleengine.o plain.o html.o form.o >> bfin-linux-uclibc-g++ table.o bookmark.o dns.o gif.o jpeg.o png.o >> bfin-linux-uclibc-g++ imgbuf.o image.o menu.o dpiapi.o findbar.o >> bfin-linux-uclibc-g++ xembed.o ../dlib/libDlib.a ../dpip/libDpip.a >> bfin-linux-uclibc-g++ IO/libDiof.a ../dw/libDw-widgets.a >> bfin-linux-uclibc-g++ ../dw/libDw-fltk.a ../dw/libDw-core.a >> bfin-linux-uclibc-g++ ../lout/liblout.a -ljpeg -lpng12 >> bfin-linux-uclibc-g++ -L/home/mheiser/fltk-2.0.x-r6841/lib >> bfin-linux-uclibc-g++ -Wl,-rpath,/home/mheiser/bfin-fltk2/lib >> bfin-linux-uclibc-g++ -lfltk2_images -lpng -lfltk2_images -ljpeg -lz >> bfin-linux-uclibc-g++ -lfltk2 >> bfin-linux-uclibc-g++ -L/home/mheiser/uClinux/uclinux-dist/user/microw >> bfin-linux-uclibc-g++ in/nxlib/nxlib-0.45 >> bfin-linux-uclibc-g++ -L/home/mheiser/uClinux/uclinux-dist/user/microw >> bfin-linux-uclibc-g++ in/src/lib >> bfin-linux-uclibc-g++ -L/home/mheiser/uClinux/uclinux-dist/staging/usr >> bfin-linux-uclibc-g++ /lib -lX11 -lpthread -lm -lnano-X -lsupc++ -lz >> bfin-linux-uclibc-g++ -liconv >> /home/mheiser/fltk-2.0.x-r6841/lib/libfltk2.so: undefined reference to >> `_Xutf8LookupString' >> /home/mheiser/fltk-2.0.x-r6841/lib/libfltk2.so: undefined reference to >> `_XFreeDeviceList' >> /home/mheiser/fltk-2.0.x-r6841/lib/libfltk2.so: undefined reference to >> `_wcstombs' >> /home/mheiser/fltk-2.0.x-r6841/lib/libfltk2.so: undefined reference to >> `_mbstowcs' >> /home/mheiser/fltk-2.0.x-r6841/lib/libfltk2.so: undefined reference to >> `_XOpenDevice' >> /home/mheiser/fltk-2.0.x-r6841/lib/libfltk2.so: undefined reference to >> `_XGetExtensionVersion' >> /home/mheiser/fltk-2.0.x-r6841/lib/libfltk2.so: undefined reference to >> `_XListInputDevices' >> /home/mheiser/fltk-2.0.x-r6841/lib/libfltk2.so: undefined reference to >> `_XSelectExtensionEvent' > > Aren't you missing libXi-devel? > > Regards, > Michal > >> collect2: ld gab 1 als Ende-Status zur?ck >> make[3]: *** [dillo] Fehler 1 >> make[3]: Leaving directory `/home/mheiser/dillo-2.1.1/src' >> make[2]: *** [all-recursive] Fehler 1 >> make[2]: Leaving directory `/home/mheiser/dillo-2.1.1/src' >> make[1]: *** [all-recursive] Fehler 1 >> make[1]: Leaving directory `/home/mheiser/dillo-2.1.1' >> make: *** [all] Fehler 2 >> >> Can you give me an advice? I don't know exactly where I should begin >> searching for advice.... >> >> Regards >> >> Michael >> >> -----Urspr?ngliche Nachricht----- >> Von: corvid [mailto:corvid@lavabit.com] >> Gesendet: Donnerstag, 13. August 2009 02:10 >> An: Heiser Michael >> Betreff: Re: [Dillo-dev] Crosscompiling Dillo2 for uClinux on Blackfin >> >> If you get it working from that document mentioned on the uclinux >> forum, let us know so that I can add to Compatibility.html :) >> >> >> >> Von AVG ?berpr?ft - www.avg.de >> Version: 8.5.386 / Virendatenbank: 270.13.53/2299 - Ausgabedatum: >> 08/12/09 18:12:00 >> >> _______________________________________________ >> Dillo-dev mailing list >> Dillo-dev(a)dillo.org >> http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >> > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev > > Eingehende eMail ist virenfrei. > Von AVG ?berpr?ft - www.avg.de > Version: 8.5.392 / Virendatenbank: 270.13.55/2301 - Ausgabedatum: 08/13/09 > 18:16:00 > > Eingehende eMail ist virenfrei. > Von AVG ?berpr?ft - www.avg.de > Version: 8.5.392 / Virendatenbank: 270.13.55/2301 - Ausgabedatum: 08/13/09 > 18:16:00 > Eingehende eMail ist virenfrei. Von AVG ?berpr?ft - www.avg.de Version: 8.5.392 / Virendatenbank: 270.13.55/2301 - Ausgabedatum: 08/13/09 18:16:00

1 0

Crosscompiling Dillo2 for uClinux on Blackfin
by heisermi＠hs-albsig.de Aug. 12, 2009

Aug. 12, 2009

Hi guys, Currently I'm searching for a small footprint webbrowser to use on my blackin device. This device is driven by uClinux. The first positive I can tell you is, that I compiled fltk2 for blackfin with success. I followed the instructions on tw.myblog.yahoo.com/stevegigijoe/article<http://tw.myblog.yahoo.com/stevegigijoe/article?mid=138&prev=-1&next=137> to compile and run fltk2. My modifications can be read at https://blackfin.uclinux.org/gf/project/uclinux-dist/forum/?_forum_action=F… So now I'm facing a problem with the configure script of dillo. I had to make few changes to configure.in to recognize crosscompiled Fltk2 lib. These changes went ok but when configure checks libz, then it crashes because it can't find right version of the library. So my question is, how can I tell configure to search in my uClinux directory where the library already is persistent for use with uClinux. Best Regards from Germany, Michae

1 0

Re: patch: media_type pref
by corvid＠lavabit.com Aug. 5, 2009

Aug. 5, 2009

Jorge wrote: > On Mon, Feb 16, 2009 at 05:37:36AM +0000, corvid wrote: > > It makes more sense to have a pref that the user can > > control than for us to guess what they might like > > based on screen size or whatever, I think. > > I hesitate on this. For instance: if media_type is defined to > "handheld" and there's no such remote CSS, at least it should > fallback to "screen". If there is a handheld style sheet available and dillo is running on a handheld, it would be a shame not to use it. I'm hoping that the page author would have the sense to supply something for type "all". > Maybe it's more practical to provide custom stylesheets (as the > current "style.css". e.g. small_screen.css, print.css) and to > allow switching among them from the "Tools" menu. > > What do you think? I think someone using handheld would want to use both the page author's handheld-specific code and a user style suitable for their device. I'll send this to the list in case anyone with experience using such devices with the web has opinions to share.

3 3

Re: dillo bug 916
by corvid＠lavabit.com Aug. 3, 2009

Aug. 3, 2009

Scott wrote: > As far as I can tell, it works correctly with the patch applied. :) Scott had reported: "Dillo sometimes raises its window when clicked, instead of letting the window manager do its job. Usually if I have a window partially hidden, I don't want it raised... Apps should not try to do their own window management." fltk's Window::handle() has: #if USE_X11 case PUSH: // Unused clicks should raise the window. Windows unfortunatly // raises the window on *all* clicks so we don't bother except on X. if (shown()) XMapRaised(xdisplay, i->xid); #endif Aforementioned patch attached.

3 6

experimental patch: Re: dillo2 wrapping Chinese
by corvid＠lavabit.com Aug. 2, 2009

Aug. 2, 2009

I made yet another version of this patch the other day, and furaisanjin was kind enough to run on it a bit and ensure it's doing what we want. With the previous version, compiling without optimization, gprof showed 3-4% loss of speed on a page that's mostly English text. - I removed the strdup/free from the common case. - For nonideographic, it goes character by character instead of checking every byte. This should help for, e.g., Russian, but means some 'unnecessary' length-checking in the mostly-ASCII case. And gprof suggested the slowdown might be 3% now, although at this point, unless someone is paying you to perform a lot of careful, drudgery-filled runs, it gets hard to pick the signal out of the noise when examining the time spent in relevant functions. I tried adding in some code to bypass the ideographic call for ASCII, but 1) it made the code a little messy 2) it looked like it might be saving a few tenths of a percent 3) the compiler might perform optimizations under certain circumstances making my efforts unnecessary or counterproductive. I could definitely be talked into this one, though. I tried adding an addText() with a length argument and thought it might help by saving me the trouble of writing NULL bytes into the strings and saving the trouble of some strlen()ning in dw. I couldn't see any difference in speed, although it did make things cleaner and I would want to add it in eventually if this all makes it into the repository. There will be a duplicated ideographic() test, for instance, if a word starts with digits and ends with some Japanese characters. 1) uncommon 2) complexity This patch is really two patches because it also handles the case where whitespace numeric character references are inside a word, but I wanted to see the effects of both and they are each an excuse for the overhead of the loop. I'd split it into two pieces if committing it.

2 1

Re: dillo crash at dlib/dlib.c:173
by stevegigijoe＠yahoo.com.tw July 29, 2009

July 29, 2009

Hello guys I'm Sorry. Corvid is right. I must mass up something :p Steve ______________________________________________________________________________________________________ ¥I¶O€~®e¶qµL€W¡HYahoo!©_Œ¯¹q€l«Hœc2.0§K¶Oµ¹§A¡A«H¥ó¥Ã»·€£¥²§R¡I http://tw.mg0.mail.yahoo.com/dc/landing

1 0

dillo crash at dlib/dlib.c:173
by stevegigijoe＠yahoo.com.tw July 29, 2009

July 29, 2009

Hello all After update, the dillo crash while opening http://www.google.com.tw on dlib/dlib.c:173 The array haystack is null and unchecked cause the problem... Log as below gigijoe@user-desktop:~/dillo2$ gdb src/dillo GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (gdb) r Starting program: /home/gigijoe/dillo2/src/dillo [Thread debugging using libthread_db enabled] paths: Cannot open file '/home/gigijoe/.dillo/keysrc' paths: Cannot open file '/usr/local/etc/dillo/keysrc' paths: Using internal defaults... dillo_dns_init: Here we go! (threaded) Disabling cookies. Nav_open_url: new url='http://www.google.com.tw' [New Thread 0xb795b8e0 (LWP 11430)] [New Thread 0xb782bb90 (LWP 11433)] Dns_server [0]: www.google.com.tw is 74.125.19.105 74.125.19.106 74.125.19.99 74.125.19.104 74.125.19.103 74.125.19.147 [Thread 0xb782bb90 (LWP 11433) exited] Connecting to 74.125.19.105 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb795b8e0 (LWP 11430)] 0x0807ee7c in dStristr (haystack=0x0, needle=0x810c13f "javascript") at dlib.c:173 173 for (i = 0, j = 0; haystack[i] && needle[j]; ++i) Current language: auto; currently c (gdb) q The program is running. Exit anyway? (y or n) y Steve ______________________________________________________________________________________________________ ¥I¶O€~®e¶qµL€W¡HYahoo!©_Œ¯¹q€l«Hœc2.0§K¶Oµ¹§A¡A«H¥ó¥Ã»·€£¥²§R¡I http://tw.mg0.mail.yahoo.com/dc/landing

3 2

dIsspace
by corvid＠lavabit.com July 27, 2009

July 27, 2009

When are we supposed to use isspace() and when are we supposed to use dIsspace()? It appears that one is now used in the C++ code and the other in the C code, but I don't know the reason for this distinction.

3 6

exit codes
by corvid＠lavabit.com July 24, 2009

July 24, 2009

I checked what bash sees when dillo returns -1 for bad cmdline argument, and $? shows 255. It seems that out of range values turn into 255. Not that anyone will ever care beyond zero vs nonzero, but I'd like to change it to something valid. I could change it to 1...or 2...or I could use the values from sysexits.h (i.e., borrow their values as opposed to including it, since it doesn't appear to be standard). Any opinions?

1 0