Date: Sat, 3 Jun 2006 04:53:29 GMT From: Tim Daneliuk <tundra@tundaware.com> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/98415: Port name problem Message-ID: <200606030453.k534rTC0082259@www.freebsd.org> Resent-Message-ID: <200606030500.k5350YWw099815@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 98415 >Category: ports >Synopsis: Port name problem >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jun 03 05:00:28 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Tim Daneliuk >Release: 4.11-Stable >Organization: TundraWare Inc. >Environment: FreeBSD eskimo.tundraware.com 4.11-STABLE FreeBSD 4.11-STABLE #29: Fri Jun 2 16:33:32 CDT 2006 toor@eskimo.tundraware.com:/usr/obj/usr1/src/sys/ESKIMO i386 >Description: Many packages depend on the presence of the 'pkgconfig' tools. However, for some reason, the port has recently been renamed to 'pkg-config'. This is causing all manner of aggravation because pre-compiled packages expect the former to be installed and don't know that the latter is the same thing. This means you have to go into the *ports* to build everything you want by hand - ports (like pango, cairo, etc.) properly look for the dependent binaries and libraries not the installed package name. What gives? >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200606030453.k534rTC0082259>