February 2003 - Dillo-dev - lists.mailman3.com

[PATCH] Some patches for configure.in
by Patrice Mandin March 19, 2003

March 19, 2003

Hello everybody, Here are 2 small patches for Dillo: - The first one add necessary stuff to do cross-compilation easy. - The other one just modify the detection for glib/gtk, because the way it is currently done pollutes the CFLAGS variable: When you have gtk/glib missing, libjpeg is not detected. Note: I am the one who ported Dillo to Atari MiNT m68k platform. But it does not work correctly. This is why I did not notice it to you. -- Patrice Mandin WWW: http://membres.lycos.fr/pmandin/ Programmeur Linux, Atari Spécialité: Développement, jeux

2 1

ipv6 and dns threads
by Damien Couderc March 15, 2003

March 15, 2003

You will found at the following URL patches from the openbsd port : http://www.openbsd.org/cgi-bin/cvsweb/ports/www/dillo/patches/ Some of them fix ipv6 and threaded name resolution bugs. I've also informed jcid that display on sparc64 is fucked as the text is displayed one word per line. All comment to fix this bug is welcome even if it's just a place where to begin to find out what is going on. Regards, Damien

2 1

freezing of dillo.0.7.0
by robert w hall March 6, 2003

March 6, 2003

Is the description of the 'freezing' of dillo given in the README an uptodate description of the problem. This implies that it is a kernel version effect... I originally compiled dillo0.6.6 against slack 7, kernel 2.4.5 (IIRC, or even 2.2.18) with no problems. However dillo0.7.0 does freeze, even when compiled against the headers for, and run under, kernel 2.4.19. BUT it compiles and runs ok when compiled under slack8.1, with the same headers and kernel. Is this a gcc problem? (I'm using 2.91.66 with slack 7). (The suggested patch poll-fix-fast of course does not run in cleanly against 0.7.0., and though the source compiles the executable still freezes). Sorry if I've missed something on this. Bob Hall PS it all compiles fine on the playstation2 linux kit with the 2.2.21 kernel, and a real old gcc -- robert w hall

2 3

Loosing bookmarks
by John Bradford March 2, 2003

March 2, 2003

Since I started using using 7.0, my bookmarks have been lost on four occasions, but I haven't been able to reproduce the bug at will - has anybody else noticed this? John.

9 9

Where can I find the flock->lockf patch?
by 阿贵 Feb. 26, 2003

Feb. 26, 2003

dillo-devHi, I'm going to build dillo on Windows, using Cygwin as porting tool and running envrionment. Guided by http://homepage.ntlworld.com/steven.obrien2/, I can build dillo-0.6.5 successfully. But there is no implmentation for lockf on Cygwin. So I'd like to know where can I find the flock->lockf patch. I want to apply a reverse patch on the new version of dillo. TIA. BTW: Please cc me, I'm not on the list. Hansom Young

1 0

Re: [Dillo-dev] segmentation fault
by andi Feb. 26, 2003

Feb. 26, 2003

> try a "real" compiler :-) ... 2.96 is not a real release (see > also http://gcc.gnu.org/gcc-2.96.html) I think redhat has > something like kcc or kgcc which is intended for kernel > compilation, but it is an official release. Ah i did not know about kgcc, thanks. I did not work either. Same problem, kgcc is gcc version egcs-2.91.66 by the way.

2 1

segmentation fault
by andi Feb. 26, 2003

Feb. 26, 2003

Hi, Thanks for this great project, i love dillo. There is just one problem with the 0.7 version. I get a segmentation fault every time i click on a link. I newly compiled dillo-0.7.0 without any errors and i starts perfectly, but if i move my mouse over a link the url in the status bar is follow by "?135070228,-1073744832" without the quotes and the numbers may vary. If i click on the link dillo exits permanently. If i type in any urls in the address field, there is no problem. Everything loads happily. --Output if i run it from the console: bash-2.05a$ ./dillo Setting locale to C... HTML warning: URL has 4 illegal characters (0x00-0x1F, 0x7F or space) HTML warning: hexadecimal color lacks leading '#' HTML warning: hexadecimal color is not in RRGGBB format. HTML warning: hexadecimal color lacks leading '#' HTML warning: hexadecimal color is not in RRGGBB format. dillorc:11: unexpected string constant "text-color", expected symbol dillorc:11: error: unexpected string constant "text-color", expected symbol dillo_dns_init: Here we go! The cookies file has a file lock: disabling cookies in this dillo! Nav_open_url: Url=>about:splash< IO_write: Changing io->Buf (4096) IO_write: EAGAIN IO_write: Changing io->Buf (4096) IO_write: EAGAIN Segmentation fault --My Versions: RedHat 7.3 GNU Make version 3.79.1 gcc version 2.96

1 0

Re: [Dillo-dev] present but cannot be compiled
by Akim Demaille Feb. 26, 2003

Feb. 26, 2003

| Hi, | there is probably something wrong with your mailer :-) | And there is no response, just the quotation ... | Jan Yes, I forgot the following piece of text, sorry: Please, report this to the package maintainers, as it's a configure.ac problem. The Autoconf 2.57 doc says: Previous versions of Autoconf merely checked whether the header was accepted by the preprocessor. This was changed because the old test was inappropriate for typical uses. Headers are typically used to compile, not merely to preprocess, and the old behavior sometimes accepted headers that clashed at compile-time. If you need to check whether a header is preprocessable, you can use `AC_PREPROC_IFELSE' (*note Running the Preprocessor::). This scheme, which improves the robustness of the test, also requires that you make sure that headers that must be included before the HEADER-FILE be part of the INCLUDES, (*note Default Includes::). If looking for `bar.h', which requires that `foo.h' be included before if it exists, we suggest the following scheme: AC_CHECK_HEADERS([foo.h]) AC_CHECK_HEADERS([bar.h], [], [], [#if HAVE_FOO_H # include <foo.h> # endif ]) Thanks! | On Feb 26 11:30:24, Akim Demaille wrote: : :| Hi, :| is is what I get with the current CVS (viz later). :| :| know that I don't have libpng, libjpeg etc installed :| y mistake, I was compiling on machine without them), :| t I mean the 'usability ... yes ; presence ... no' problem. :| this an autoconf bug, or is configure.in written badly ? :| :| e system is: :| :| Debian unstable :| kernel 2.4.19 (self compiled) :| autoconf 2.57 :| automake 1.6.3 :| gcc/cpp 3.2.2 :| :| :| e results follow. :| :| Jan :| :| :| s co dillo && cd dillo :| autogen.sh :| configure --prefix=$HOME :| ecking for a BSD-compatible install... /usr/bin/install -c :| ecking whether build environment is sane... yes :| ecking for gawk... gawk :| ecking whether make sets $(MAKE)... yes :| ecking for gcc... gcc :| ecking for C compiler default output... a.out :| ecking whether the C compiler works... yes :| ecking whether we are cross compiling... no :| ecking for suffix of executables... :| ecking for suffix of object files... o :| ecking whether we are using the GNU C compiler... yes :| ecking whether gcc accepts -g... yes :| ecking for gcc option to accept ANSI C... none needed :| ecking for style of include used by make... GNU :| ecking dependency style of gcc... gcc3 :| ecking for gcc option to accept ANSI C... none needed :| ecking for ranlib... ranlib :| ecking for gtk-config... /usr/bin/gtk-config :| ecking for GTK - version >= 1.2.0... yes :| ecking for jpeg_destroy_decompress in -ljpeg... no :| nfigure: WARNING: *** JPEG support will not be included *** :| ecking for pthread_create in -lpthread... yes :| ecking for zlibVersion in -lz... no :| ecking for png_check_sig in -lpng... no :| ecking for ANSI C header files... no :| ecking fcntl.h usability... yes :| ecking fcntl.h presence... no :| nfigure: WARNING: fcntl.h: accepted by the compiler, rejected by the preprocessor! :| nfigure: WARNING: fcntl.h: proceeding with the preprocessor's result :| nfigure: WARNING: ## ------------------------------------ ## :| nfigure: WARNING: ## Report this to bug-autoconf(a)gnu.org. ## :| nfigure: WARNING: ## ------------------------------------ ## :| ecking for fcntl.h... no :| ecking unistd.h usability... yes :| ecking unistd.h presence... no :| nfigure: WARNING: unistd.h: accepted by the compiler, rejected by the preprocessor! :| nfigure: WARNING: unistd.h: proceeding with the preprocessor's result :| nfigure: WARNING: ## ------------------------------------ ## :| nfigure: WARNING: ## Report this to bug-autoconf(a)gnu.org. ## :| nfigure: WARNING: ## ------------------------------------ ## :| ecking for unistd.h... no :| ecking sys/uio.h usability... yes :| ecking sys/uio.h presence... no :| nfigure: WARNING: sys/uio.h: accepted by the compiler, rejected by the preprocessor! :| nfigure: WARNING: sys/uio.h: proceeding with the preprocessor's result :| nfigure: WARNING: ## ------------------------------------ ## :| nfigure: WARNING: ## Report this to bug-autoconf(a)gnu.org. ## :| nfigure: WARNING: ## ------------------------------------ ## :| ecking for sys/uio.h... no :| ecking for socket... yes :| nfigure: creating ./config.status :| nfig.status: creating Makefile :| nfig.status: creating doc/Makefile :| nfig.status: creating src/Makefile :| nfig.status: creating src/IO/Makefile :| nfig.status: creating config.h :| nfig.status: executing depfiles commands :| :| : :_______________________________________________ :Dillo-dev mailing list :Dillo-dev@lists.auriga.wearlab.de :http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

1 0

configure problems
by Jan Stary Feb. 26, 2003

Feb. 26, 2003

Hi, this is what I get with the current CVS (viz later). I know that I don't have libpng, libjpeg etc installed (by mistake, I was compiling on machine without them), but I mean the 'usability ... yes ; presence ... no' problem. Is this an autoconf bug, or is configure.in written badly ? The system is: Debian unstable kernel 2.4.19 (self compiled) autoconf 2.57 automake 1.6.3 gcc/cpp 3.2.2 The results follow. Jan cvs co dillo && cd dillo ./autogen.sh ./configure --prefix=$HOME checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for gcc option to accept ANSI C... none needed checking for ranlib... ranlib checking for gtk-config... /usr/bin/gtk-config checking for GTK - version >= 1.2.0... yes checking for jpeg_destroy_decompress in -ljpeg... no configure: WARNING: *** JPEG support will not be included *** checking for pthread_create in -lpthread... yes checking for zlibVersion in -lz... no checking for png_check_sig in -lpng... no checking for ANSI C header files... no checking fcntl.h usability... yes checking fcntl.h presence... no configure: WARNING: fcntl.h: accepted by the compiler, rejected by the preprocessor! configure: WARNING: fcntl.h: proceeding with the preprocessor's result configure: WARNING: ## ------------------------------------ ## configure: WARNING: ## Report this to bug-autoconf(a)gnu.org. ## configure: WARNING: ## ------------------------------------ ## checking for fcntl.h... no checking unistd.h usability... yes checking unistd.h presence... no configure: WARNING: unistd.h: accepted by the compiler, rejected by the preprocessor! configure: WARNING: unistd.h: proceeding with the preprocessor's result configure: WARNING: ## ------------------------------------ ## configure: WARNING: ## Report this to bug-autoconf(a)gnu.org. ## configure: WARNING: ## ------------------------------------ ## checking for unistd.h... no checking sys/uio.h usability... yes checking sys/uio.h presence... no configure: WARNING: sys/uio.h: accepted by the compiler, rejected by the preprocessor! configure: WARNING: sys/uio.h: proceeding with the preprocessor's result configure: WARNING: ## ------------------------------------ ## configure: WARNING: ## Report this to bug-autoconf(a)gnu.org. ## configure: WARNING: ## ------------------------------------ ## checking for sys/uio.h... no checking for socket... yes configure: creating ./config.status config.status: creating Makefile config.status: creating doc/Makefile config.status: creating src/Makefile config.status: creating src/IO/Makefile config.status: creating config.h config.status: executing depfiles commands

3 2

Website improvement / CVS page
by Sebastian Leske Feb. 22, 2003

Feb. 22, 2003

Hi, as I could not find some webmaster contact address at the website at http://dillo.auriga.wearlab.de/ , I'm posting to this list. I like the idea of providing some information on how to checkout the CVS version of dillo, so people without CVS experience can try it out. However, the information about CVS given on http://dillo.auriga.wearlab.de/cvs.html is incomplete. The page give the command to to a checkout, but it neglects to mention that you first have to do a login with an empty password. I'd propose you change the page to read: Check out from our server at wearLab! Just run these two commands: cvs -z3 -d:pserver:anonymous@auriga.wearlab.de:/sfhome/cvs/dillo login cvs -z3 -d:pserver:anonymous@auriga.wearlab.de:/sfhome/cvs/dillo co dillo When prompted for a password, just press Return. A new directory will be created with the current CVS version of dillo. Greetings and keep up the good work on Dillo! S.Leske PS: Please CC me on replies, I'm not subscribed.

3 4