Date: Tue, 24 Aug 2010 07:32:49 +0800 (CST) From: Denny Lin <dennylin93@hs.ntnu.edu.tw> To: FreeBSD-gnats-submit@FreeBSD.org Cc: skreuzer@FreeBSD.org Subject: ports/149924: [PATCH] Workaround for configure bug in devel/distcc Message-ID: <20100823233249.068214B781B@mail.hs.ntnu.edu.tw> Resent-Message-ID: <201008232340.o7NNe1Ar033767@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 149924 >Category: ports >Synopsis: [PATCH] Workaround for configure bug in devel/distcc >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Aug 23 23:40:01 UTC 2010 >Closed-Date: >Last-Modified: >Originator: Denny Lin >Release: FreeBSD 8.0-RELEASE-p4 amd64 >Organization: >Environment: System: FreeBSD cnmc32.hs.ntnu.edu.tw 8.0-RELEASE-p4 FreeBSD 8.0-RELEASE-p4 #0: Tue Jul 13 22:41:29 CST 2010 root@cnmc32.hs.ntnu.edu.tw:/usr/obj/usr/src/sys/CNMC32 amd64 >Description: There is a bug in configure, so ENABLE_RFC2553 is still defined when --disable-rfc2553 is in use. When ENABLE_RFC2553 is defined, distccd cannot bind IPv4 addresses. Since RFC2553 is disabled by default, we can comment out --disable-rfc2553 as a temporary solution. >How-To-Repeat: >Fix: --- distcc.patch begins here --- diff -ru distcc.orig/Makefile distcc/Makefile --- distcc.orig/Makefile 2010-08-24 07:26:51.000000000 +0800 +++ distcc/Makefile 2010-08-24 07:28:04.000000000 +0800 @@ -43,7 +43,9 @@ .endif .if defined(WITHOUT_RFC2553) -CONFIGURE_ARGS+= --disable-rfc2553 +# Temporary workaround for configure bug: +# ENABLE_RFC2553 is defined when --disable-rfc2553 is used. +#CONFIGURE_ARGS+= --disable-rfc2553 .else CONFIGURE_ARGS+= --enable-rfc2553 .endif --- distcc.patch ends here --- >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100823233249.068214B781B>