From owner-freebsd-ports@freebsd.org Wed Mar 27 01:47:38 2019 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1A3D15661DD for ; Wed, 27 Mar 2019 01:47:38 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 350598F6DB; Wed, 27 Mar 2019 01:47:36 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id x2R1klJt092949 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 26 Mar 2019 18:46:49 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id x2R1klx2092948; Tue, 26 Mar 2019 18:46:47 -0700 (PDT) (envelope-from fbsd) Date: Tue, 26 Mar 2019 18:46:47 -0700 From: bob prohaska To: "Bradley T. Hughes" Cc: Jonathan Chen , freebsd-ports@freebsd.org Subject: Re: Can't compile www/node on rpi2 Message-ID: <20190327014647.GB90710@www.zefox.net> References: <20190323213940.GA74509@www.zefox.net> <20190326021459.GA87373@www.zefox.net> <8be4cab4-febb-17d6-fa6c-422fb8085b78@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8be4cab4-febb-17d6-fa6c-422fb8085b78@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-Rspamd-Queue-Id: 350598F6DB X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [4.29 / 15.00]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; IP_SCORE(0.15)[ip: (0.55), ipnet: 50.1.16.0/20(0.27), asn: 7065(-0.02), country: US(-0.07)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.84)[0.837,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.53)[0.528,0]; MX_GOOD(-0.01)[cached: www.zefox.net]; NEURAL_SPAM_LONG(0.88)[0.884,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Mar 2019 01:47:39 -0000 On Tue, Mar 26, 2019 at 08:07:48PM +0100, Bradley T. Hughes wrote: > > > On 2019-03-26 19:07, Jonathan Chen wrote: > > On Wed, 27 Mar 2019 at 00:24, Bradley T. Hughes wrote: > >> On 2019-03-26 03:14, bob prohaska wrote: > >>> On Mon, Mar 25, 2019 at 10:23:26PM +0100, Bradley T. Hughes wrote: > >> > >> Looks like you need to upgrade www/libnghttp2 as well. :) > >> > >>> Thanks for reading, I'd be pleased to try any experiments suggested. > >> > >> In general, www/node requires that all dependencies are up-to-date. The > >> port doesn't explicitly list minimum versions of its dependencies, but I > >> am beginning to think that it should (this is not the first time I have > >> seen this kind of problem). > > > > You shouldn't have to list the minimum version for dependencies. If > > someone is following the tip of the ports tree, it is expected that > > all the port dependencies are up to date when building a port. Not sure I understand this statement. How can one know the port's dependencies until a build (or something equivalent) is attempted? I'd understand the statement better if there were some way to identify and check out "consistent" versions of the ports tree, for a particular port and revision. Is such a thing possible? > All the > > port-management tools in ports-mgmt assume this, and build > > port-dependancies as required. When building ports, it is always best > > to use one of the build-tools (ie: poudriere, synth , portmaster) > > instead of by hand. > I've played a little with portmaster, and it seemed more prone to stopping unintentionally than a simple "make -DBATCH" in the port directory. IIRC, it always stopped on stale but installed dependencies. Perhaps I'm doing somthing dumb, but I couldn't figure out what it was. Could it merely be the fact that I'm using a Raspberry Pi 2 or 3? > I may not have to, no, but since I have had a couple of reports about > build errors due to out-of-date dependencies, I can help out fellow > users by giving them a helpful message instead of a daunting build error. > > Right? :) > Amen! Informative error messages are a huge help. Library names easily associated with the port that made them would be another large help. Some are obvious, but a few have been real headscratchers. Thank you! bob prohaska