After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 132242 - libcroco-0.4.0 pc-file corrupt ....
libcroco-0.4.0 pc-file corrupt ....
Status: RESOLVED FIXED
Product: libcroco
Classification: Core
Component: General
unspecified
Other opensolaris
: Normal blocker
: ---
Assigned To: libcroco maintainers
libcroco maintainers
Depends on:
Blocks:
 
 
Reported: 2004-01-22 22:27 UTC by Jonas Jonsson
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Description Jonas Jonsson 2004-01-22 22:27:33 UTC 
The following should be in the libcroco.pc file that is generated, if not
librsvg cannot be built ......

Cflags: -I${includedir}/libcroco -I${includedir}/libcroco/seleng
-I${includedir}/libcroco/parser
Comment 1 Mike Castle 2004-01-28 01:24:49 UTC 
I just ran into this problem, too.  (I was checking bugzilla for it
when I found this report).

I suspect the problem is that the source ships with a libcroco.pc that
sets prefix=/usr/local

But, for me, I build outside of the srcdir, and so I end up with
libcroco.pc in srcdir and libcroco.pc in builddir, and they're
definitely different.

I suspect that if I delete libcroco.pc from srcdir after unpacking,
that it will install a correct version.

Will test shortly.
Comment 2 Mike Castle 2004-01-28 01:29:09 UTC 
Doh!  I'm an idiot.

I still had the build laying around, so I just deleted the .pc from
srcdir, and did a make install from builddir.

pkg-config --cflags libcroco now lists the proper directories.

Should be careful not to ship pregenerated files (outside of those
from autotools).
Comment 3 Dodji Seketeli 2004-03-03 23:43:24 UTC 
This should be fixed in the CVS Head now.

Thank you for reporting this.

Dodji.