From owner-freebsd-arm@freebsd.org Wed Mar 15 15:58:15 2017 Return-Path: Delivered-To: freebsd-arm@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 CE96ED0D4CB for ; Wed, 15 Mar 2017 15:58:15 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ABD0C1674; Wed, 15 Mar 2017 15:58:15 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id F28A1754; Wed, 15 Mar 2017 15:58:14 +0000 (UTC) Date: Wed, 15 Mar 2017 16:58:14 +0100 From: Baptiste Daroussin To: Jia-Shiun Li Cc: Kyle Evans , "freebsd-arm@freebsd.org" Subject: Re: portsnap failing on armv6 Message-ID: <20170315155814.mav2bvs45ol73itq@ivaldir.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="nf5vctws3kridk4g" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170225 (1.8.0) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2017 15:58:15 -0000 --nf5vctws3kridk4g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 15, 2017 at 06:00:51PM +0800, Jia-Shiun Li wrote: > Hi Kyle, >=20 > I simply rebuilt and replaced diff and the result is the same. > According to portsnap source and its output, it suggests lam > is to blame, not diff as r315197 implied. Or do I need to > build something else? >=20 > -Jia-Shiun. >=20 >=20 There was an issue with lam(1) as well (not my fault this time :)) and I fixed it anyway in r315309. Best regards, Bapt --nf5vctws3kridk4g Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAljJZJAACgkQY4mL3PG3 PloGJRAA1XxME0aQfDqUdlKEFzlcz0t+bDazZiHDt7LlQXCt1fuolyVjRgCsVXiX jrMECanQnRwRzaMf8kjSB1MjyO5LXti5i7xv78DjjknXbR9xiI1637E8z/f7mF9M P+EVEFwGj18XRGOy2cttOcjVRcgJqtGZG2sE1sWpPcRUH+I2nrIFNRLZx2DN00wO i/HsO3bCoyWL7IctEZJHzDvqyza/AHIIZcECIn0NHRODp6UQqC58oHnTkZlLXARl j8wOwwO/iN6gjHBj5l1FMoexHEkTjd1DLvZo5Hu6oWz1secDpFpQfA43CBuTRZZn o9nllukcY/gy1y75k4AJAUdgO5YV/6wjn9WMHrtSOIJxof0h3ff85vKU/R6m3kjK VODjKgJ/6oHMWlJVAaXGqsD3gcmb9dV7P0LfHYYIkUlHnfElyVZQO4nHDyLwL83U 7f2svGYYhhhJKy0MC/LJB5h+DGFkaFp+Lx39FcMZpMUzJykyp7vNtvYaKJymQS/I lFZ834BE/kWIyC74Plgsn7OC3PPlVhHeer47djWDwW0h45rT4mf2ynxy8pevj56a ASfZC9X9HcOlBtZ+VpoKd0SHZ3u27bBfb5g3NeIQdHYARXZO2kMANr+Ly8V6hvGn oLhvCOLWFUnllsagMgY0BGyJDMb2Ub/INcSYU1PQqSLZRzdm17k= =B5uR -----END PGP SIGNATURE----- --nf5vctws3kridk4g--