From owner-freebsd-questions@freebsd.org Fri Oct 6 18:36:49 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 594B3E3E43D for ; Fri, 6 Oct 2017 18:36:49 +0000 (UTC) (envelope-from dalescott@shaw.ca) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 309CE6A3FF for ; Fri, 6 Oct 2017 18:36:48 +0000 (UTC) (envelope-from dalescott@shaw.ca) Received: from dalet420 ([174.0.43.39]) by shaw.ca with SMTP id 0XUMebuGOM9gt0XUNeJBdl; Fri, 06 Oct 2017 12:36:47 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shaw.ca; s=s20150330; t=1507315007; bh=Zj6ajfPzYxNJAl/YdP/07zXB7WpG60dBDzkUWmzp+hc=; h=From:To:References:In-Reply-To:Subject:Date; b=q25QBlbP5exSQLi6Nii201n52lelmezo95vLX8q0jP5v0GL7DCOGjPc8alJ4ISOhC 49fXQ/slI06eQOgeyELWarYnXjtayUEjRyj//v88YbluLy7XBRVRn5kBO/fPPRcZfs 6IxqFmKnY065fLZxJc/Xv1agZ2RYEzGCTAgSzgoKzCT6NpSXlA4EHJQv7aOaonK91i yjlUGABiSvfEC/tKb7p3NQzI/HoAzEMtQIAvTkD5UN/beB3CSf3KecCb0L6FVa1Z1n 6zZQT2no7WKUZrk5t81ftjdVZ6lcUY6DJ1peoxQvTbGeZA5YykHgk3+SVkIevA1w6A lbPuIUKiANypQ== X-Authority-Analysis: v=2.2 cv=a+JAzQaF c=1 sm=1 tr=0 a=TiBur8m8wieNAdBnNdHE5Q==:117 a=TiBur8m8wieNAdBnNdHE5Q==:17 a=kj9zAlcOel0A:10 a=x7bEGLp0ZPQA:10 a=5mcg790sAAAA:8 a=jU4qhlNgAAAA:8 a=ZeieZHtt2CBu6FNDXqIA:9 a=CjuIK1q_8ugA:10 a=uQeDYW1NI25gHNlrW_eK:22 From: "Dale Scott" To: References: <1507310201.4831.52.camel@btinternet.com> In-Reply-To: Subject: RE: Cannot .configure WindowMaker 0.95.8 - Xmu lib issues Date: Fri, 6 Oct 2017 12:36:47 -0600 Message-ID: <019401d33ed2$11b78350$352689f0$@shaw.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGxIc42nRpzbWUtPBSPwzJ7DTLAXAEL8bq3oxL6XEA= Content-Language: en-us X-CMAE-Envelope: MS4wfDR/zyx5LQwlj3N7qOVZAqpiF2kwrq0yJP3rEL6IKyMcKz4BCH2M+sfI8900M8ExwWMiQgUjzUm330pYxQuD4kaAIAomPMCfCBXX/wKjjZg6nxf/R2/7 XjeTQ3x6hI2x0WopFLeLmWV0zd3c4uVvpEVyMH/dGNiPgfiJSzlzpMQu X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 18:36:49 -0000 > You should only build and install software by ports or pkg in FreeBSD. So the > port needs an update. My first choice for installing an application is _always_ a package, followed by compiling from source in the ports tree when a specific compile option not available as a port is required (I compile openldap-server from the ports tree to configure using BDB which has been deprecated). However, there will certainly come a time when an application is only available as a source tarball from the dev project team. There is no technical reason requiring you to install applications only using packages or ports, but do expect that software not available as a package or port will be more trouble to build and install. If the application was created for Linux, you may need to install and configure the GNU build chain first, and also expect to encounter problems along the way. Experiment first in a VM (e.g. create a VM in VirtualBox using a backup of your FreeBSD system or a distribution ISO), and only work on a critical machine if you have a backup (and have proven it can be restored!). Good luck! Dale --- Transparency with Trust Blog: http://www.dalescott.net LinkedIn: https://ca.linkedin.com/in/dalescott