Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the PkgConfig CPAN distribution.

Report information
The Basics
Id: 75698
Status: resolved
Priority: 0/
Queue: PkgConfig
People
Owner: Nobody in particular
Requestors: rsimoes [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: 0.07120

History Show all quoted text
  Sun Mar 11 16:53:46 2012 rsimoes [...] cpan.org - Ticket created
Subject: Add pkg-config's own path to default list
.pc files for some libraries--especially those installed by package managers--end up in "/usr/lib/[CANONICAL SYSTEM NAME]/pkgconfig". There is, for example, "/usr/lib/x86_64-linux-gnu/pkgconfig" on my home machine, which happens to contain libidn.pc. pkg-config is naturally able to find it, while PkgConfig.pm requires that directory to be added via the "search_path" option.
  Tue Mar 13 00:38:49 2012 MNUNBERG [...] cpan.org - Correspondence added
The problem with doing so is that this is mainly a GNU convention. What if someone wanted a 32-bit pkgconfig directory? these things get kinda hairy. It might make sense to try and determine this via the parameters in $^O and friends.. On Sun Mar 11 16:53:46 2012, rsimoes wrote: Show quoted text
> .pc files for some libraries--especially those installed by package > managers--end up in "/usr/lib/[CANONICAL SYSTEM NAME]/pkgconfig". > > There is, for example, "/usr/lib/x86_64-linux-gnu/pkgconfig" on my home > machine, which happens to contain libidn.pc. pkg-config is naturally > able to find it, while PkgConfig.pm requires that directory to be added > via the "search_path" option.
  Tue Mar 13 00:38:50 2012 The RT System itself - Status changed from 'new' to 'open'
  Tue Feb 04 06:53:00 2014 PLICEASE [...] cpan.org - Correspondence added
On Debian 7 at least you can get the system name thusly: pacific% dpkg-architecture -qDEB_HOST_MULTIARCH x86_64-linux-gnu When pkg-config is built as a .deb file for Debian it seems to hardcode the appropriate path, there doesn't seem to be a config file that can be consulted, which would be ideal. how or if this be integrated into PkgConfig I am not sure. I would rather not have to execute a program to determine the system name. RPM based systems would be different again. On Sun Mar 11 16:53:46 2012, rsimoes wrote: Show quoted text
> .pc files for some libraries--especially those installed by package > managers--end up in "/usr/lib/[CANONICAL SYSTEM NAME]/pkgconfig". > > There is, for example, "/usr/lib/x86_64-linux-gnu/pkgconfig" on my home > machine, which happens to contain libidn.pc. pkg-config is naturally > able to find it, while PkgConfig.pm requires that directory to be added > via the "search_path" option.
  Tue Mar 25 16:33:05 2014 PLICEASE [...] cpan.org - Correspondence added
On Sun Mar 11 16:53:46 2012, rsimoes wrote: Show quoted text
> .pc files for some libraries--especially those installed by package > managers--end up in "/usr/lib/[CANONICAL SYSTEM NAME]/pkgconfig". > > There is, for example, "/usr/lib/x86_64-linux-gnu/pkgconfig" on my home > machine, which happens to contain libidn.pc. pkg-config is naturally > able to find it, while PkgConfig.pm requires that directory to be added > via the "search_path" option.
I believe that 0.07020 resolves this issue. If you have a chance can you please try it out and let me know.
  Mon Apr 14 04:18:58 2014 PLICEASE [...] cpan.org - Correspondence added
Show quoted text
> I believe that 0.07020 resolves this issue. If you have a chance can > you please try it out and let me know.
resolving
  Mon Apr 14 04:18:59 2014 PLICEASE [...] cpan.org - Status changed from 'open' to 'resolved'
  Mon Apr 14 04:18:59 2014 PLICEASE [...] cpan.org - Fixed in 0.07120 added