From owner-freebsd-ports-bugs@FreeBSD.ORG Tue Aug 13 14:40:02 2013 Return-Path: Delivered-To: freebsd-ports-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3BE3C46C for ; Tue, 13 Aug 2013 14:40:02 +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 292362B54 for ; Tue, 13 Aug 2013 14:40:02 +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 r7DEe1pG032103 for ; Tue, 13 Aug 2013 14:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r7DEe1pf032102; Tue, 13 Aug 2013 14:40:01 GMT (envelope-from gnats) Date: Tue, 13 Aug 2013 14:40:01 GMT Message-Id: <201308131440.r7DEe1pf032102@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org Cc: From: Marc Peters Subject: Re: ports/180651: net/scribe won't build with automake update to 1.14 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Marc Peters List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Aug 2013 14:40:02 -0000 The following reply was made to PR ports/180651; it has been noted by GNATS. From: Marc Peters To: bug-followup@FreeBSD.org, Marc Peters , jnlin@csie.nctu.edu.tw Cc: Subject: Re: ports/180651: net/scribe won't build with automake update to 1.14 Date: Tue, 13 Aug 2013 16:29:57 +0200 A user at http://forums.freebsd.org/showthread.php?p=229818#post229818 suggested the following: "The bug is due to scribe calling AM_INIT_AUTOMAKE in both the top of configure.ac and inside FB_INITIALIZE defined in acinclude.m4. The solution is to comment either the AM_INIT_AUTOMAKE or FB_INITIALIZE in the top of configure.ac. They should not both be called." Maybe this will fix the issues and the portmaintainer create a patch for the port. Cheers, Marc