From owner-freebsd-ports@FreeBSD.ORG Wed Oct 30 18:46:31 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 910F6B9E for ; Wed, 30 Oct 2013 18:46:31 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6B17A2A85 for ; Wed, 30 Oct 2013 18:46:31 +0000 (UTC) Received: by mail-pa0-f43.google.com with SMTP id hz1so1366274pad.30 for ; Wed, 30 Oct 2013 11:46:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=P4uqFQ4Am/5ceFTKgrRaIar4L6dzXrEtwew3aj6YbWY=; b=Z46sSpvBAUJTqvfb69PK6HH5H7sqlmKlRvG+/zSil45ve1YbeEtMxtBBuCF3av7LZk eblYieYofxvGFvXWSZCNMLrCKcGFoGXXD4G2E8DLlc341kjlH3sqbtimj8VQbMfPI0aq ZvPS09SFZ/bionBpYv5Whg/bRPycuvrrb2Jgkgrjfmc0Y83AoCFTPP2BTHBUqk7LeOYg WMMpaDW0LR8gwbbYMtjwOIw8Qnc3BgVGsTBRkwpc11ndp0+iWLiJFlVrlITTzgHGjCe1 q/ebX5lnBpJg+yN2L11/d6D0Id0WmYtqoWbiNkEiD2iIQtPAgaybp1yYnRxHfkNkF3nR K9wA== MIME-Version: 1.0 X-Received: by 10.68.190.229 with SMTP id gt5mr3670798pbc.177.1383158790941; Wed, 30 Oct 2013 11:46:30 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.67.23.101 with HTTP; Wed, 30 Oct 2013 11:46:30 -0700 (PDT) Date: Wed, 30 Oct 2013 11:46:30 -0700 X-Google-Sender-Auth: A1t1jrpa_qg-Av5nGmH1kw5RoLY Message-ID: Subject: Problems dealing with ports use of pkgconf From: Kevin Oberman To: FreeBSD Ports ML Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Oct 2013 18:46:31 -0000 I have run into a dilemma in regards to the use of pkgconf in ports. Here is what has bitten me: To allow sftp to get files, multimedia/vlc uses libssh2. libssh2, in turn, uses openssl or the GNU crypto library. If i have installed securith/openssl, all is well, but I don't want of need the security/openssl port. If I have not installed openssl from ports, vlc fails! Here is why: libssh2 creates a .pc file to allow other packages to know whether it uses openssl or libgcrypt. this is a nice thing, but it makes the common assumption that openssl is only there if the package has been installed. I believe that is is the case for Linux. Not so for FreeBSD. vlc uses pkgconf to check on whether all required libraries are installed for libssh2. I finds that libssh2 requires libssl: Requires.private: libssl,libcrypto It then checks to see if these are installed. Since libssl is not installed, it bails on the error. (I believe that it shoudl be "Required: rather than Requires.private:, but that has no impact on the problem. Since FreeBSD ports have already checked the dependencies before building a port, I think such checks should be removed from ports, but I'm not familiar enough with the real-world implications of this to know if it is the right way to go. If it is, I'll can submit a patch for vlc. I suspect, after reading the developers comments, that libssh2 developers will not want to remove their recent changes in this area. -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com