From owner-freebsd-ports-bugs@FreeBSD.ORG Mon Aug 26 00:30:01 2013 Return-Path: Delivered-To: freebsd-ports-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9525425B for ; Mon, 26 Aug 2013 00:30:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 82C562BF2 for ; Mon, 26 Aug 2013 00:30:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r7Q0U1Ro025951 for ; Mon, 26 Aug 2013 00:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r7Q0U0LV025950; Mon, 26 Aug 2013 00:30:00 GMT (envelope-from gnats) Date: Mon, 26 Aug 2013 00:30:00 GMT Message-Id: <201308260030.r7Q0U0LV025950@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org Cc: From: Rodrigo OSORIO Subject: Re: ports/181010: net-mgmt/smokeping 2.6.9 build problem X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Rodrigo OSORIO List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2013 00:30:01 -0000 The following reply was made to PR ports/181010; it has been noted by GNATS. From: Rodrigo OSORIO To: Bill Thiede Cc: bug-followup@FreeBSD.org Subject: Re: ports/181010: net-mgmt/smokeping 2.6.9 build problem Date: Mon, 26 Aug 2013 02:29:28 +0200 Hi, I'm just back from holiday, and didn't check too much my email during this period. First, thanks for your investigations, specially the PR link, this can explain why it works for me since I did all my test using a fresh install with a port tree up-to-dated. So that confirm my first analyze, it was a dependency issue, and there is nothing to change in smokeping port. If you agree, this issue can be closed without delay. Best regards, - rodrigo