From owner-freebsd-ports-bugs@freebsd.org  Tue Jun 28 00:09:16 2016
Return-Path: <owner-freebsd-ports-bugs@freebsd.org>
Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7ADBB81D8A
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Tue, 28 Jun 2016 00:09:16 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id B77A72980
 for <freebsd-ports-bugs@FreeBSD.org>; Tue, 28 Jun 2016 00:09:16 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u5S09Fsh090125
 for <freebsd-ports-bugs@FreeBSD.org>; Tue, 28 Jun 2016 00:09:16 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 210648] sysutils/slurm-wlm build hangs
Date: Tue, 28 Jun 2016 00:09:16 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: jrm@ftfl.ca
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Flags: maintainer-feedback?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-210648-13-u0rsqmdk7L@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-210648-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-210648-13@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jun 2016 00:09:16 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210648

--- Comment #2 from Joseph Mingrone <jrm@ftfl.ca> ---
The problem is with the upstream autoconf scripts.  They try to be "helpful=
" by
dynamically installing components based on environment.  However, for some =
of
these options there is no explicit argument to turn installation on or off.

I've been communicating with upstream and there may be a fix soon.  I may a=
lso
try to fix the autoconf scripts myself.  In the meantime, you can build the
port in a clean environment (e.g. with poudriere) or install the package.

--=20
You are receiving this mail because:
You are the assignee for the bug.=