From owner-freebsd-current@freebsd.org Tue Nov 7 17:13:00 2017 Return-Path: Delivered-To: freebsd-current@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 AB87BE5E3B4 for ; Tue, 7 Nov 2017 17:13:00 +0000 (UTC) (envelope-from prvs=4775ea590=roger.pau@citrix.com) Received: from SMTP.CITRIX.COM.AU (smtp.citrix.com.au [103.14.252.240]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "DigiCert SHA2 Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CF4AF779B8; Tue, 7 Nov 2017 17:12:58 +0000 (UTC) (envelope-from prvs=4775ea590=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.44,359,1505779200"; d="scan'208";a="106697492" Date: Tue, 7 Nov 2017 17:12:50 +0000 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: Glen Barber CC: Subject: Re: make ftp failing Message-ID: <20171107171250.zytoitfstpno3d44@dhcp-3-128.uk.xensource.com> References: <20171107113901.mfv6f5wis3pagmou@dhcp-3-128.uk.xensource.com> <20171107141530.GB56652@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20171107141530.GB56652@FreeBSD.org> User-Agent: NeoMutt/20171013 X-ClientProxiedBy: AMSPEX02CAS01.citrite.net (10.69.22.112) To AMSPEX02CL03.citrite.net (10.69.22.127) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Nov 2017 17:13:00 -0000 On Tue, Nov 07, 2017 at 02:15:30PM +0000, Glen Barber wrote: > On Tue, Nov 07, 2017 at 11:39:01AM +0000, Roger Pau Monné wrote: > > Hello, > > > > Since the end of last week `make -C release ftp` has been failing for > > me, giving the following output (trimmed for convenience): > > > [...] > > /usr/bin/ld: cannot find -lvers > > cc: error: linker command failed with exit code 1 (use -v to see invocation) > > *** Error code 1 > > > > I hit this problem yesterday against r325363. What revision is this > against? Upgrading to at least r325457 should fix it. Thanks, this is indeed fixed now. The logs provided where from the last run during the weekend. Roger.