Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 07 Jul 2011 03:12:37 +0200
From:      Matthias Andree <mandree@FreeBSD.org>
To:        FreeBSD-gnats-submit@FreeBSD.org
Cc:        mm@FreeBSD.org
Subject:   ports/158715: www/lighttpd: consider USE_GMAKE=yes 
Message-ID:  <E1Qed8v-000LYu-4h@apollo.emma.line.org>
Resent-Message-ID: <201107080310.p683A2hM016851@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         158715
>Category:       ports
>Synopsis:       www/lighttpd: consider USE_GMAKE=yes
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jul 08 03:10:01 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator:     Matthias Andree
>Release:        FreeBSD 8.2-STABLE amd64
>Organization:
>Environment:
System: FreeBSD apollo.emma.line.org 8.2-STABLE FreeBSD 8.2-STABLE #5: Fri Jul 1 02:39:55 CEST 2011 toor@apollo.emma.line.org:/usr/obj/usr/src/sys/GENERIC amd64


	
>Description:
Hi Martin,

during build (with FORCE_MAKE_JOBS on a quadcore) I've seen the usual
config.status being rerun AFTER the build. This is an artifact that
happens with BSD make, but not GNU make. Reasons I don't know.
(The obvious trigger is re-running autotools on the sources,
possibly with confusing timestamps or whatever.)

In order to get an authentic build, consider setting USE_GMAKE=yes.

Thanks for your attention :)
	
>How-To-Repeat:
	
>Fix:

	


>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1Qed8v-000LYu-4h>