From owner-freebsd-ports@FreeBSD.ORG Thu Apr 9 18:31:51 2015 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F12972B7; Thu, 9 Apr 2015 18:31:51 +0000 (UTC) Received: from biertje.skysmurf.nl (unknown [IPv6:2001:984:78b5:1:21b:78ff:fea8:3f22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 880B726B; Thu, 9 Apr 2015 18:31:51 +0000 (UTC) Received: from biertje.skysmurf.nl (localhost [127.0.0.1]) by biertje.skysmurf.nl (8.14.9/8.14.9) with ESMTP id t39IVlZh036498; Thu, 9 Apr 2015 20:31:47 +0200 (CEST) (envelope-from fonz@biertje.skysmurf.nl) Received: (from fonz@localhost) by biertje.skysmurf.nl (8.14.9/8.14.9/Submit) id t39IVlWn036497; Thu, 9 Apr 2015 20:31:47 +0200 (CEST) (envelope-from fonz) Date: Thu, 9 Apr 2015 20:31:47 +0200 From: "A.J. \"Fonz\" van Werven" To: Bryan Drewery Subject: Re: FreeBSD Port: valgrind-3.10.0.20150126_1,1 Message-ID: <20150409183147.GA36468@biertje.skysmurf.nl> References: <5526BD4D.2040304@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="RnlQjJ0d97Da+TV1" Content-Disposition: inline In-Reply-To: <5526BD4D.2040304@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "ports@FreeBSD.org" , Pracheth Javali X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Apr 2015 18:31:52 -0000 --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Bryan Drewery wrote: >> Is there a valgrind port for mips64/freebsd platform? >=20 > There is only devel/valgrind. There is the ONLY_FOR_ARCHS line in the > Makefile. There's also devel/valgrind-devel ;-) But it has the same ONLY_FOR_ARCHS line. Unfortunately both are unmaintained, but perhaps whoever maintained these ports when that line appeared might know more. If I'm not mistaken the most recent version of Valgrind has Linux mips64 support, but FreeBSD mips64 support is probably experimental at best. AvW --=20 I'm not completely useless, I can be used as a bad example. --RnlQjJ0d97Da+TV1 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVJsWSAAoJEAfP7gJTaCe8gzQQAMShtyU60zMXcScdc+v7FwQ3 zN0y82DL5ZH2pXTzsihvYsWc7+hPQRJzjZf9JeHTnjf/dGzIGD9mqjqCaT6m8kQz bjSgDDNVa6RXUY+RMRaMX50dbhqUKwi4VMlBoexX9P7yhe1yBAc4B19wNGsRRklu 53mMyCKS8c5EK3JgVcOwimQJj0czirRUPb2QfbxzWRG4+bpBE/Gmsptva2HsZU/t udEw+ebwG6150f6hMCTDgCuG9l70IXdQjiNNAsqqZnmJHUo309sCSKkZ8sbPzzKU fEybGsuh29HFnuhVHMU90NmE87xBVbHnb7linNiS2sADqXlZsFjMGFby0GQcU7U4 vi3xDD9IABR5lVcpJaNkOYT33xTaw/Rx2zWSYhthZfRyX2ygu3m1gxksasy2y3fF S9bhS+FcNnIqfvZ39EmPzHMyidDjyln26RyoUuCdu/cpeFeUy9X+GhKvinWbV0lS YCaO5hxoHRZi0CEh8wAof3oauB4mYnww5fyy63QwEOFrFqIDK/0Es6RYjsdhOy2N 5Tzash9vuCeKbMZayl9CwQbpH4TfJKwQY8iC+jfXvQygicI/R0CqLA2OA70EILw3 6Lp1bwiHUHSnjigniiRJwjpi06GOki+hecLO0XgRLX0LFCKYIqWU8xwzilUbNTRd Gg7nSVPOMqu5t5wYT5Py =ghsn -----END PGP SIGNATURE----- --RnlQjJ0d97Da+TV1--