Your message dated Mon, 21 Jul 2008 14:36:24 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#440941: pkg-config: --with-installed-glib must not be 
used
has caused the Debian Bug report #440941,
regarding pkg-config: --with-installed-glib must not be used
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
440941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=440941
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: pkg-config
Version: 0.22-1
Severity: normal

pkg-config package uses --with-installed-glib configure option. It breaks 
horribly in one case: when you 
are trying to build your private copy of glib with debian pkg-config, and your 
private copy is broken at 
the moment. 

E.g. you set up LD_LIBRARY_PATH, you build glib, install it into some prefix, 
*then* break it 
(remove a dependency lib in my case, so the libglib-2.0.so is unusable at the 
moment), and try to rebuild 
it. Glib configure needs pkg-config, pkg-config is linked to broken glib, dead 
end.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages pkg-config depends on:
ii  libc6                         2.6.1-1+b1 GNU C Library: Shared libraries

pkg-config recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
]] Yevgen Muntyan 

| pkg-config package uses --with-installed-glib configure option. It
| breaks horribly in one case: when you are trying to build your
| private copy of glib with debian pkg-config, and your private copy
| is broken at the moment.

Don't do that then?

| E.g. you set up LD_LIBRARY_PATH, you build glib, install it into
| some prefix, *then* break it (remove a dependency lib in my case, so
| the libglib-2.0.so is unusable at the moment), and try to rebuild
| it. Glib configure needs pkg-config, pkg-config is linked to broken
| glib, dead end.

Unset LD_LIBRARY_PATH, use glib from packaging system and it'll work
just fine.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are


--- End Message ---

Reply via email to