GNOME Bugzilla – Bug 447252
evince-0.9.0 won't build: compile error in ev-poppler:1632
Last modified: 2007-06-13 21:58:34 UTC
Steps to reproduce: configure make Stack trace: Not relevant (yet). Other information: I've tried to build garnome's evince (svn-trunk) on an i686 using gcc-4.2.0. The build dies as logged below. For what it's worth, I've got poppler-0.5.9, poppler-data-0.1 and glib-2.13.4 installed. Here's the log: /usr/bin/g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I../../libdocument -pthread -DORBIT2=1 -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -I/opt/garnome-svn/include/gtk-2.0 -I/opt/garnome-svn/lib/gtk-2.0/include -I/opt/garnome-svn/include/atk-1.0 -I/opt/garnome-svn/include/cairo -I/opt/garnome-svn/include/pango-1.0 -I/opt/garnome-svn/include -I/usr/X11R6/include -I/opt/garnome-svn/include/glib-2.0 -I/opt/garnome-svn/lib/glib-2.0/include -I/opt/garnome-svn/include/freetype2 -I/opt/garnome-svn/include/gnome-vfs-2.0 -I/opt/garnome-svn/lib/gnome-vfs-2.0/include -I/opt/garnome-svn/include/gconf/2 -I/opt/garnome-svn/include/orbit-2.0 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/opt/garnome-svn/include/libgnome-2.0 -I/opt/garnome-svn/include/orbit-2.0 -I/opt/garnome-svn/include/gconf/2 -I/opt/garnome-svn/include/gnome-vfs-2.0 -I/opt/garnome-svn/lib/gnome-vfs-2.0/include -I/opt/garnome-svn/include/glib-2.0 -I/opt/garnome-svn/lib/glib-2.0/include -I/opt/garnome-svn/include/libbonobo-2.0 -I/opt/garnome-svn/include/bonobo-activation-2.0 -DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -I/opt/garnome-svn/include/poppler/glib -I/opt/garnome-svn/include/poppler -I/opt/garnome-svn/include/gtk-2.0 -I/opt/garnome-svn/lib/gtk-2.0/include -I/opt/garnome-svn/include/cairo -I/opt/garnome-svn/include/glib-2.0 -I/opt/garnome-svn/lib/glib-2.0/include -I/opt/garnome-svn/include/pango-1.0 -I/opt/garnome-svn/include -I/usr/X11R6/include -I/opt/garnome-svn/include/freetype2 -I/usr/include/libpng12 -I/opt/garnome-svn/include -L/opt/garnome-svn/lib -O2 -g -pipe -Wall -Wno-unused -I/opt/garnome-svn/include -I/opt/garnome-svn/include -L/opt/garnome-svn/lib -O2 -g -pipe -MT ev-poppler.lo -MD -MP -MF .deps/ev-poppler.Tpo -c ev-poppler.cc -fPIC -DPIC -o .libs/ev-poppler.o ev-poppler.cc: In function 'void pdf_selection_render_selection(EvSelection*, EvRenderContext*, GdkPixbuf**, EvRectangle*, EvRectangle*, GdkColor*, GdkColor*)': ev-poppler.cc:1632: error: cannot convert 'gdouble' to 'cairo_t*' for argument '2' to 'void poppler_page_render_selection(PopplerPage*, cairo_t*, PopplerRectangle*, PopplerRectangle*, PopplerSelectionStyle, GdkColor*, GdkColor*)' make[4]: *** [ev-poppler.lo] Error 1 make[4]: Leaving directory `/home/ronis/Project/notar/GNOME/garnome/desktop/evince/work/main.d/evince-0.9.0/backend/pdf'
Are you compiling evince 0.9 or svn trunk? evince 0.9 won't compile against poppler 0.5.9 because poppler API has changed. If you are compiling svn trunk, make sure to run autogen.sh script before.
I'm compiling 0.9 which is currently part of garnome's svn trunk. Hopefully this can be changed.
Any chance of a new unstable evince release, so both code-bases (evince and poppler) that are supposed to go into GNOME 2.20 get some testing? This is important for both, GARNOME and the official 2.19 release sets, which depend on tarball releases. (FWIW, tarballs for 2.19.4 are due Monday.)
Sure there will be release, why are you worrying?
(In reply to comment #3) > Any chance of a new unstable evince release, so both code-bases (evince and > poppler) that are supposed to go into GNOME 2.20 get some testing? yes, sure > This is important for both, GARNOME and the official 2.19 release sets, which > depend on tarball releases. > > (FWIW, tarballs for 2.19.4 are due Monday.) > Exactly, we have planned to release for GNOME 2.19.4.
Great!!! GARNOME likes to smoke test the bleeding edge. -Joseph
(In reply to comment #4) > Sure there will be release, why are you worrying? Nickolay, I'm not worrying. :) I just asked, because I don't know about your schedule. In any case, the reason is given in comment 3. (In reply to comment #5) > Exactly, we have planned to release for GNOME 2.19.4. Great, thanks! According to comment 1, this is fixed in SVN, thus closing RESOLVED FIXED. Tarballs expected soon. Thanks for your fast response, guys. :)
Ups, sorry. We'll try to do all the best. Thanks again for your wonderful support.
Don't worry, Nickolay. This is unstable, and occasional breakage is to be expected. ;) Also, you're welcome. GARNOME is dedicated to serve the GNOME community, and constantly smoke-testing to get smooth releases -- even unstable ones. (with my Bugsquad and GARNOME maintainer hat on)