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 134537 - gar.conf.mk overwrites PKG_CONFIG_PATH
gar.conf.mk overwrites PKG_CONFIG_PATH
Status: RESOLVED FIXED
Product: GARNOME
Classification: Deprecated
Component: general
unspecified
Other Windows
: Normal normal
: ---
Assigned To: Jeff Waugh
garnome list
Depends on:
Blocks:
 
 
Reported: 2004-02-16 16:14 UTC by Matt Lavin
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Description Matt Lavin 2004-02-16 16:14:58 UTC 
If there is already a PKG_CONFIG_PATH variable set in the enviroment when
garnome is used it will be ignored.  

In gar.conf.mk a new PKG_CONFIG_PATH is created without reference to the
current varaiable.  

This is a problem when the user has installed X into some non-standard
location, such as /opt/XFree86-4.4RC2/.  It would be nice to be able to use
gnarome as follows

> PKG_CONFIG_PATH=/opt/XFree86-4.4RC2/lib/pkgconfig make paranoid-install

but it will not find any Xfree pkg files.
Comment 1 Jeff Waugh 2004-02-17 03:06:42 UTC 
Thanks, I've made sure the current one is added to the end of the
variable in the makefile like so:

PKG_CONFIG_PATH :=
$(DESTDIR)$(libdir)/pkgconfig:/usr/lib/pkgconfig:$(PKG_CONFIG_PATH)
Comment 2 Ron Smits 2004-02-18 07:52:28 UTC 
hmmz can't you make it an option just like build_clean and
garchivedir? Personally I like having the build contained like this
Comment 3 Jeff Waugh 2004-02-18 11:16:19 UTC 
It will be if what it requires is in your GARNOME prefix, that's why
the existing PKG_CONFIG_PATH is plopped in last. :-)