Created attachment 31811 [details] compile log When compiling cairo from git I get: CC cairo-ft-font.o cairo-ft-font.c: In function ‘_get_bitmap_surface’: cairo-ft-font.c:1091: error: ‘subpixel’ undeclared (first use in this function) cairo-ft-font.c:1091: error: (Each undeclared identifier is reported only once cairo-ft-font.c:1091: error: for each function it appears in.) I'm using gcc (Gentoo 4.4.2 p1.0) 4.4.2 on gentoo, amd64 with the x11-overlay (which pulls everything from git): [ebuild U ] x11-libs/cairo-9999 [1.8.8] USE="X cleartype glitz opengl svg xcb -debug -directfb -doc" Which translates into updating from 1.8.8 to "9999" (git) and the "USE"-flags translate into the following configure call: ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --enable-xlib --disable-gtk-doc --disable-directfb --enable-xcb --enable-svg --enable-glitz --enable-xlib-xrender --disable-test-surfaces --enable-pdf --enable-png --enable-ft --enable-ps I think it's just a variable not being declared in _get_bitmap_surface() (or in an enclosing block).
(In reply to comment #0) > Created an attachment (id=31811) [details] > compile log This line in the compile log looks quite suspect: "Applying cairo-1.2.4-lcd-cleartype-like.diff" Can you please check if the code compiles correctly if you don't apply that patch?
(In reply to comment #1) > (In reply to comment #0) > > Created an attachment (id=31811) [details] [details] > > compile log > This line in the compile log looks quite suspect: > "Applying cairo-1.2.4-lcd-cleartype-like.diff" > Can you please check if the code compiles correctly if you don't apply that > patch? Compiles fine now. That patch contained the broken code. Thanks for you help and sorry for the niose. Going to report this to the gentoo-devs. Bye, Daniel
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.