Ramakrishnan Muthukrishnan writes:
> it will be great if this bug can be fixed in a new upload. Some of the
> software like the new guile upstream, depends on pkg-config to throw
> the right paths for compiling and linking.
Hey Christoph,
Now that Guile 2.0's been released, I'll need a libgc-de
Hi,
it will be great if this bug can be fixed in a new upload. Some of the
software like the new guile upstream, depends on pkg-config to throw
the right paths for compiling and linking.
Thanks
Ramakrishnan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject o
Rebuilding with the following applied does the trick.
diff --git a/debian/libgc-dev.install b/debian/libgc-dev.install
index 0daebed..8287a36 100644
--- a/debian/libgc-dev.install
+++ b/debian/libgc-dev.install
@@ -2,6 +2,7 @@ usr/include
usr/lib/libgc*.so
usr/lib/libgc*.a
usr/lib/libgc*.la
+us
Package: libgc-dev
Version: 1:7.1-1
Severity: normal
The upstream source tarballs (at least 7.0 and 7.1) come with a
pkg-config file (bdw-gc.pc), which are installed on a source build,
but missing from the Debian package; this prevents software using
pkg-config to detect libgc and according compi
4 matches
Mail list logo
