From owner-freebsd-ports@freebsd.org Sat Sep 16 08:35:17 2017 Return-Path: Delivered-To: freebsd-ports@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 213FAE07F40 for ; Sat, 16 Sep 2017 08:35:17 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.227]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "dnvrco-oedge-vip.email.rr.com", Issuer "dnvrco-oedge-vip.email.rr.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 045B96DA6D for ; Sat, 16 Sep 2017 08:35:16 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from [74.134.208.22] ([74.134.208.22:41097] helo=localhost) by dnvrco-omsmta02 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id 73/10-25924-C32ECB95; Sat, 16 Sep 2017 08:35:09 +0000 Date: Sat, 16 Sep 2017 08:35:04 +0000 Message-ID: <73.10.25924.C32ECB95@dnvrco-omsmta02> From: "Thomas Mueller" To: freebsd-ports@freebsd.org Subject: Re: synth install ... builds but does not always install named packages References: <8C.42.25924.3928BB95@dnvrco-omsmta02> <20170915074220.GA1995@gmail.com> <4C.CD.25924.D0E8BB95@dnvrco-omsmta02> X-RR-Connecting-IP: 107.14.64.7:25 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Sep 2017 08:35:17 -0000 > On 16 September 2017 at 09:01, Thomas Mueller wrote: > > Some of the packages not installed are widespread build dependencies, such as nasm, and are better installed than rebuilt or temporarily reinstalled every time. > synth doesn't rebuild build-dependencies if it isn't required. It > stores the dependancies as a packages in the local package repository > and unpacks it for each build. In fact, there is no need to install > build dependancies on your local system, as it will *never* get used > by synth, as synth uses a clean chroot'd environment for all its > builds. > [...] > > And then it was irritating when some specifically named packages were not installed (math/gnumeric, editors/abiword-docs, mail/metamail, for instance). > I would check: > 1. did the packages get built, and are present in the local package repository. > 2. what sort of error messages you are getting from just a "pkg > install ${package}" from the local package repo. > Cheers. > Jonathan Chen Those packages that were built but not installed appeared in /var/synth/live-packages/All , otherwise I would not have complained about failure to install. I didn't "pkg install ${package}" from local package repo, I installed some by rerunning "synth install category/package" (using actual category/package names). I see also that graphics/epdfview built but didn't install, don't remember if I named this port, but would like to install it now. Maybe also graphics/evince. I still want to install build dependencies, or at least some of them, to be able to cross-compile Haiku and Linux toolchains (such as buildroot, OpenWRT, crosstool-ng, Pengutronix ptxdist and Cross Linux Fom Scratch). Their advice about host build system requirements guides me on what I need to be installed, since this is out of synth territory, out of FreeBSD ports territory. Tom