May 2013 - Dillo-dev - lists.mailman3.com

Can't compile Dillo 3.0.3

by Johannes.Hofmann＠gmx.de

On Sat, May 18, 2013 at 08:23:34PM +0200, Sebastian Geerken wrote: > On Sat, May 18, Johannes Hofmann wrote: > > On Sat, May 18, 2013 at 02:47:56PM +0200, Sebastian Geerken wrote: > > > [...] > > > > > > X11 is needed in src/xembed.cc. It seems that on most systems it is > > > linked indirectly, (src/dillo -> libfltk.so -> libX11.so), on others > > > not, so that an additional "-lX11" is necessary. Should we add it > > > generally? It does not harm; we have only to care about other systems > > > than X11. > > > > Could we check for libX11 in configure and link explicitely against > > it if available but not fail otherwise? > > That way dillo should still compile on OSX. > > I thought of this. The code is included in "#ifdef X_PROTOCOL", so > making "-lX11" depend on this X_PROTOCOL should be save; however, I've > not found where X_PROTOCOL is defined. That comes from the fltk headers depending on whether fltk was built with X11 backend or not. I don't see how we could get that information at configure time. Maybe some fltk-config option? Johannes

May 18, 2013

Can't compile Dillo 3.0.3

by sgeerken＠dillo.org

On Sat, May 18, Johannes Hofmann wrote: > On Sat, May 18, 2013 at 02:47:56PM +0200, Sebastian Geerken wrote: > > [...] > > > > X11 is needed in src/xembed.cc. It seems that on most systems it is > > linked indirectly, (src/dillo -> libfltk.so -> libX11.so), on others > > not, so that an additional "-lX11" is necessary. Should we add it > > generally? It does not harm; we have only to care about other systems > > than X11. > > Could we check for libX11 in configure and link explicitely against > it if available but not fail otherwise? > That way dillo should still compile on OSX. I thought of this. The code is included in "#ifdef X_PROTOCOL", so making "-lX11" depend on this X_PROTOCOL should be save; however, I've not found where X_PROTOCOL is defined. Sebastian

May 18, 2013

Can't compile Dillo 3.0.3

by Johannes.Hofmann＠gmx.de

On Sat, May 18, 2013 at 02:47:56PM +0200, Sebastian Geerken wrote: > On Sat, May 11, August Karlstrom wrote: > > Linking with libX11 is what's missing: > > > > LIBS=-lX11 ./configure > > make > > make install > > > > This means that libX11 needs to be added to the build scripts. > > On Mon, May 13, August Karlstrom wrote: > > This is what I get: > > > > $ fltk-config --ldflags > > -L/usr/lib/x86_64-linux-gnu -Wl,-Bsymbolic-functions -lfltk > > $ fltk-config --ldstaticflags > > -Wl,-Bsymbolic-functions /usr/lib/x86_64-linux-gnu/libfltk.a -lXext > > -lXft -lfontconfig -lfontconfig -lXinerama -ldl -lm -lX11 > > > > >The configure script of dillo uses "--ldflags", which is used for > > >dynamic linking against "libfltk.so", while "--ldstaticflags" is used > > >for linking against "libfltk.a". Which files of the two do you have in > > >the respective directory (/usr/lib/x86_64-linux-gnu/)? My guess is > > >that "libfltk.so" does not exist and so dillo is linked statically. > > > > I do have both the dynamic and the static libraries: > > > > $ ls /usr/lib/x86_64-linux-gnu/libfltk* > > /usr/lib/x86_64-linux-gnu/libfltk.a > > [..] > > /usr/lib/x86_64-linux-gnu/libfltk.so > > /usr/lib/x86_64-linux-gnu/libfltk.so.1.3 > > X11 is needed in src/xembed.cc. It seems that on most systems it is > linked indirectly, (src/dillo -> libfltk.so -> libX11.so), on others > not, so that an additional "-lX11" is necessary. Should we add it > generally? It does not harm; we have only to care about other systems > than X11. Could we check for libX11 in configure and link explicitely against it if available but not fail otherwise? That way dillo should still compile on OSX. Johannes

May 18, 2013

Problems with DuckDuckGo

by sgeerken＠dillo.org

Hi! Somehow, dillo seems to have problems with redirections from DuckDuckGo to other sites. If you search (Ctrl-S) for "foo", with standard preferences, there is no problem, while searching for "foo !i" does not work: dillo stops retrieving the URL <https://duckduckgo.com/lite/?kp=-1&q=foo+%21i>. Entering this URL in Firefox works correctly, redirecting to Google image search. Sebastian

May 18, 2013

Can't compile Dillo 3.0.3

by sgeerken＠dillo.org

On Sat, May 11, August Karlstrom wrote: > Linking with libX11 is what's missing: > > LIBS=-lX11 ./configure > make > make install > > This means that libX11 needs to be added to the build scripts. On Mon, May 13, August Karlstrom wrote: > This is what I get: > > $ fltk-config --ldflags > -L/usr/lib/x86_64-linux-gnu -Wl,-Bsymbolic-functions -lfltk > $ fltk-config --ldstaticflags > -Wl,-Bsymbolic-functions /usr/lib/x86_64-linux-gnu/libfltk.a -lXext > -lXft -lfontconfig -lfontconfig -lXinerama -ldl -lm -lX11 > > >The configure script of dillo uses "--ldflags", which is used for > >dynamic linking against "libfltk.so", while "--ldstaticflags" is used > >for linking against "libfltk.a". Which files of the two do you have in > >the respective directory (/usr/lib/x86_64-linux-gnu/)? My guess is > >that "libfltk.so" does not exist and so dillo is linked statically. > > I do have both the dynamic and the static libraries: > > $ ls /usr/lib/x86_64-linux-gnu/libfltk* > /usr/lib/x86_64-linux-gnu/libfltk.a > [..] > /usr/lib/x86_64-linux-gnu/libfltk.so > /usr/lib/x86_64-linux-gnu/libfltk.so.1.3 X11 is needed in src/xembed.cc. It seems that on most systems it is linked indirectly, (src/dillo -> libfltk.so -> libX11.so), on others not, so that an additional "-lX11" is necessary. Should we add it generally? It does not harm; we have only to care about other systems than X11. Sebastian

May 18, 2013

Can't compile Dillo 3.0.3

by fusionfile＠gmail.com

On 2013-05-13 13:21, Sebastian Geerken wrote: > On Sat, May 11, August Karlstrom wrote: >> [...] >> Linking with libX11 is what's missing: >> >> LIBS=-lX11 ./configure >> make >> make install >> >> This means that libX11 needs to be added to the build scripts. > > I've looked at the fltk-config script, and found that it has two > options: > > $ fltk-config --ldflags > -L/usr/lib/x86_64-linux-gnu -lfltk > $ fltk-config --ldstaticflags > /usr/lib/x86_64-linux-gnu/libfltk.a -lXext -lXft -lfontconfig -lfontconfig -lXinerama -ldl -lm -lX11 This is what I get: $ fltk-config --ldflags -L/usr/lib/x86_64-linux-gnu -Wl,-Bsymbolic-functions -lfltk $ fltk-config --ldstaticflags -Wl,-Bsymbolic-functions /usr/lib/x86_64-linux-gnu/libfltk.a -lXext -lXft -lfontconfig -lfontconfig -lXinerama -ldl -lm -lX11 > The configure script of dillo uses "--ldflags", which is used for > dynamic linking against "libfltk.so", while "--ldstaticflags" is used > for linking against "libfltk.a". Which files of the two do you have in > the respective directory (/usr/lib/x86_64-linux-gnu/)? My guess is > that "libfltk.so" does not exist and so dillo is linked statically. I do have both the dynamic and the static libraries: $ ls /usr/lib/x86_64-linux-gnu/libfltk* /usr/lib/x86_64-linux-gnu/libfltk.a /usr/lib/x86_64-linux-gnu/libfltk_cairo.a /usr/lib/x86_64-linux-gnu/libfltk_cairo.so /usr/lib/x86_64-linux-gnu/libfltk_cairo.so.1.3 /usr/lib/x86_64-linux-gnu/libfltk_forms.a /usr/lib/x86_64-linux-gnu/libfltk_forms.so /usr/lib/x86_64-linux-gnu/libfltk_forms.so.1.3 /usr/lib/x86_64-linux-gnu/libfltk_gl.a /usr/lib/x86_64-linux-gnu/libfltk_gl.so /usr/lib/x86_64-linux-gnu/libfltk_gl.so.1.3 /usr/lib/x86_64-linux-gnu/libfltk_images.a /usr/lib/x86_64-linux-gnu/libfltk_images.so /usr/lib/x86_64-linux-gnu/libfltk_images.so.1.3 /usr/lib/x86_64-linux-gnu/libfltk.so /usr/lib/x86_64-linux-gnu/libfltk.so.1.3 Regards, August

May 13, 2013

Can't compile Dillo 3.0.3

by sgeerken＠dillo.org

On Sat, May 11, August Karlstrom wrote: > [...] > Linking with libX11 is what's missing: > > LIBS=-lX11 ./configure > make > make install > > This means that libX11 needs to be added to the build scripts. I've looked at the fltk-config script, and found that it has two options: $ fltk-config --ldflags -L/usr/lib/x86_64-linux-gnu -lfltk $ fltk-config --ldstaticflags /usr/lib/x86_64-linux-gnu/libfltk.a -lXext -lXft -lfontconfig -lfontconfig -lXinerama -ldl -lm -lX11 The configure script of dillo uses "--ldflags", which is used for dynamic linking against "libfltk.so", while "--ldstaticflags" is used for linking against "libfltk.a". Which files of the two do you have in the respective directory (/usr/lib/x86_64-linux-gnu/)? My guess is that "libfltk.so" does not exist and so dillo is linked statically. (A simple test confirms this: renaming "libfltk.so" results in similar errors.) For this case, the configure script of dillo should be modified. My suggestions: - Generally make it possible to use "--ldstaticflags". An option for this, "--enable-static-fltk"? - There should be some tests to detect this error. Sebastian

May 13, 2013

Can't compile Dillo 3.0.3

by fusionfile＠gmail.com

On 2013-05-11 21:38, Jorge Arellano Cid wrote: > On Sat, May 11, 2013 at 06:46:53PM +0200, August Karlstrom wrote: >> Linking with libX11 is what's missing: >> >> LIBS=-lX11 ./configure >> make >> make install >> >> This means that libX11 needs to be added to the build scripts. > > I'm using Debian on amd64 and -lX11 doesn't appear in the options, > though it compiles OK, but libX11.so.6 gets linked anyway! > > (AFAICS X11 gets in indirectly by including FL/x.H in xembed.c). > > What OS are you using? Lubuntu 13.04 with Blackbox window manager. /August

May 11, 2013

Can't compile Dillo 3.0.3

by jcid＠dillo.org

On Sat, May 11, 2013 at 06:46:53PM +0200, August Karlstrom wrote: > On 2013-05-10 22:48, August Karlstrom wrote: > >On 2013-05-10 17:44, Sebastian Geerken wrote: > >>It is identical to mine (Debian wheezy amd64) except this option: > >> > >>>-Wl,-Bsymbolic-functions > >> > >>Maybe you should try it without it (simply by typing the command > >>manually). The documentation does not give a reason for hope, however > >>(man ld): > >> > >> -Bsymbolic-functions > >> When creating a shared library, bind references to global > >>function > >> symbols to the definition within the shared library, if > >>any. This > >> option is only meaningful on ELF platforms which support > >>shared > >> libraries. > > > >Unfortunately I get the same error after removing -Wl,-Bsymbolic-functions. > > Linking with libX11 is what's missing: > > LIBS=-lX11 ./configure > make > make install > > This means that libX11 needs to be added to the build scripts. I'm using Debian on amd64 and -lX11 doesn't appear in the options, though it compiles OK, but libX11.so.6 gets linked anyway! (AFAICS X11 gets in indirectly by including FL/x.H in xembed.c). What OS are you using? -- Cheers Jorge.-

May 11, 2013

Can't compile Dillo 3.0.3

by fusionfile＠gmail.com

On 2013-05-10 22:48, August Karlstrom wrote: > On 2013-05-10 17:44, Sebastian Geerken wrote: >> It is identical to mine (Debian wheezy amd64) except this option: >> >>> -Wl,-Bsymbolic-functions >> >> Maybe you should try it without it (simply by typing the command >> manually). The documentation does not give a reason for hope, however >> (man ld): >> >> -Bsymbolic-functions >> When creating a shared library, bind references to global >> function >> symbols to the definition within the shared library, if >> any. This >> option is only meaningful on ELF platforms which support >> shared >> libraries. > > Unfortunately I get the same error after removing -Wl,-Bsymbolic-functions. Linking with libX11 is what's missing: LIBS=-lX11 ./configure make make install This means that libX11 needs to be added to the build scripts. Regards, August

May 11, 2013