From owner-freebsd-ports@FreeBSD.ORG Mon Aug 3 19:24:18 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74A31106564A for ; Mon, 3 Aug 2009 19:24:18 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 05A298FC1E for ; Mon, 3 Aug 2009 19:24:17 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 21983 invoked by uid 399); 3 Aug 2009 19:24:16 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 3 Aug 2009 19:24:16 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4A77395A.4080407@FreeBSD.org> Date: Mon, 03 Aug 2009 12:24:10 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.22 (X11/20090729) MIME-Version: 1.0 To: Scott Bennett References: <200908012305.n71N5og5019876@mp.cs.niu.edu> In-Reply-To: <200908012305.n71N5og5019876@mp.cs.niu.edu> X-Enigmail-Version: 0.95.7 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: skv@freebsd.org, freebsd-ports@freebsd.org Subject: Re: recent update causes perl5.10 build failure X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Aug 2009 19:24:18 -0000 Scott Bennett wrote: > An update yesterday or today results in perl5.10's build aborting. When > it failed under portmaster, the messages from several processes were too > jumbled for me to see easily what had happened, so I tried portinstall instead. If you get a non-obvious port build failure in portmaster your next step should be to try just building the port itself without any tools (i.e., cd /usr/ports/foo/bar ; make clean ; make). That will give you the idea of whether or not the error is related to the tool, or the port itself. > At least on a first look, it seems that perl5.10 has "MAKE_JOBS_SAFE= yes" > in its Makefile, but that it should not. I changed that to > "MAKE_JOBS_SAFE= no" The ports infrastructure does not care what the value of the define is, it just cares if it is defined. You need to do this: cd /usr/ports/lang/perl5.10 vi Makefile (replace the MAKE_JOBS_SAFE with MAKE_JOBS_UNSAFE) make clean make config make Then report your results. hth, Doug -- This .signature sanitized for your protection