[Bug 1330033] Re: invalid token @CARBON_LIBS@ in glib-2.0.pc
Launchpad Bug Tracker
1330033 at bugs.launchpad.net
Wed Jun 18 18:35:48 UTC 2014
This bug was fixed in the package glib2.0 - 2.41.0-2
---------------
glib2.0 (2.41.0-2) experimental; urgency=medium
[ Andreas Henriksson ]
* Bump python:any build-dependency to >= 2.7.5-5~ (Closes: #747928)
[ Emilio Pozuelo Monfort ]
* Use the default compiler on sparc, since it's already >> 4.7.
Closes: #751313.
[ Iain Lane ]
* 0001-Prevent-an-invalid-CARBON_LIBS-from-appearing-in-the.patch:
Cherry-pick patch from upstream to fix an invalid "@CARBON_LIBS@" token
appearing in Libs.private in the pcfile. (LP: #1330033)
-- Iain Lane <laney at debian.org> Mon, 16 Jun 2014 10:17:36 +0100
** Changed in: glib2.0 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1330033
Title:
invalid token @CARBON_LIBS@ in glib-2.0.pc
Status in “glib2.0” package in Ubuntu:
Fix Released
Bug description:
In libglib2.0-dev 2.41.0-1, glib-2.0.pc contains an unexpanded token
in Libs.private:
Name: GLib
Description: C Utility Library
Version: 2.41.0
Requires.private: libpcre
Libs: -L${libdir} -lglib-2.0
Libs.private: -pthread -lpcre @CARBON_LIBS@
Cflags: -I${includedir}/glib-2.0 -I${libdir}/glib-2.0/include
This makes it impossible to statically link against glib2.0 in utopic,
though it doesn't cause problems for dynamic linking.
I ran into this problem while doing a test build of qemu. I'm not
entirely sure why Libs.private was used, given that qemu dynamically
links against glib2.0, but it's definitely still a bug in glib2.0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1330033/+subscriptions
More information about the foundations-bugs
mailing list