Hi
Config.log says that cairo isn't available as symbols from libfreetype
aren't found while linking libcairo in.
Maybe it's because of recent XF4 changes? Anyone else has similar
problem?
Important parts from build log:
[]
checking for cairo >= 0.5.2-head yes
checking CAIRCFLAGS -I/usr/local/include/cairo
checking CAIRLIBS -L/usr/local/lib -lcairo
checking for in -lcairo no
checking for cairo_ft_scaled_font_lock_face in -lcairo no
[]
Error in package: "/" does not exist
Error in package: "/" does not exist
Error in package: "/" does not exist
Error in package: "/" does not exist
Error in package: "/" does not exist
[]
Full build log is attached.
Following diff fixes this problem for me
Index: Makefile
RCS file: /cvs/ports/devel/pango/Makefile,v
retrieving revision 1.15
diff -u -r1.15 Makefile
Makefile1 Dec 2005 15:41:09 -00001.15
Makefile1 Jan 2006 15:20:35 -0000
@@ -33,7 +33,8 @@
CNFIGURE_ARGS+=
CNFIGURE_ARGS+=
CNFIGURE_ENV=CPPFLAGS="-I${X11BASE}/include" \
-PKG_CNFIG_PATH="${LCALBASE}/lib/pkgconfig:${X11BASE}/lib/pkgconfig"
+PKG_CNFIG_PATH="${LCALBASE}/lib/pkgconfig" \
+LDFLAGS="-L${X11BASE}/lib -lfreetype"
post-install:
@${INSTALL_DATA_DIR} ${PREFIX}/share/examples/pango; \

Sun, 1 Jan 2006, Aleksander Piotrowski wrote:

Config.log says that cairo isn't available as symbols from libfreetype
aren't found while linking libcairo in.

Maybe it's because of recent XF4 changes? Anyone else has similar
problem?

What snapshot are you using? I had no issues on a Dec 30 snap.

Marc

Marc Matteo wrote:
>Config.log says that cairo isn't available as symbols from libfreetype
>aren't found while linking libcairo in.
>>
>Maybe it's because of recent XF4 changes? Anyone else has similar
>problem?

What snapshot are you using? I had no issues on a Dec 30 snap.

I've seen this as well, but not on snapshots but really recent -current.
That is, I've seen it around the same time Aleksander mailed this in. I
rebuilt XF4 after the freefont (or freetype?) update reached me through
cvsync.de.openbsd.org yesterday, somewhen around noon CET.

Haven't investigated a lot (not even tried Aleks' fix, "so much time and
so little to do"), and my first and probably wrong guess was that
cairo's SHARED_LIBS patch may have caused fallout. *shrug*

Anyways, I can confirm this happened. Right now, I don't get much
further either wanted to build XF4 again, but now that build bombs
out in xedit due to some API change in the Xprint thingie. Guess stuff
is just too much in flux right now, or I broke something and there'll be
an X snapshot soon that I can use.

Moritz

1/2/06, Matthieu Herrb <matthieu.herrb (AT) laas (DOT) frwrote:

Yes. This is indeed caused by the freetype update, part of XF4 changes.
There are in fact 2 bugs revelead by this. I've already commited a fix
for the first one (freetype2.pc was incorrect).
The second one is in cairo. It's generating an incorrect cairo.pc when
freetype is located using pkg-config instead of freetype-config (the
only method available in freetype 2.1.8). Patch attached.

Now that freetype dependency is handled by pkg-config like other libs,
I think the "correct" way to fix cairo.pc is to use
"pkg-config freetype2" for "Libs:" (since -lfreetype is
not needed).
Patch attached.

Eric.

1/6/06, Matthieu Herrb <matthieu.herrb (AT) laas (DOT) frwrote:

I missed part of the discussion about your previous patch that already
tried to remove -lfreetype from Libs in cairo.pc, but I think its wrong:

- I don't understand how an application can use cairo libs without
linking explicitely against freetype, since some cairo libs call
freetype functions directly.

- one problem is that cairo provides several libs, with different
dependencies, but only one .pc file. So it has to take all dependencies
in account.

- the other problem is that BSD doesn't like to link depencencies
into a library. But this cannot be solved by pkg-config. We need to
patch libtool or automake to ignore '-l' options in pkg-config Libs when
producing a library instead of an executable.

So I think my patch was more correct. But I'll let the real ports
developpers decide.

I understand perfectly, but then cairo.pc is still broken, because
cairo also links to png, X11, z, glitz, etc. Humm, wait what if
we Change "Requires.private" to "Requires". Yes, that seems
to do it! Could it be _the_ fix?

Eric.