Bug 1086773

Summary:	configure: argp-standalone is always built, even when not needed
Product:	[Community] GlusterFS	Reporter:	Kaleb KEITHLEY <kkeithle>
Component:	build	Assignee:	Kaleb KEITHLEY <kkeithle>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	mainline	CC:	bugs, gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.6.0beta1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-11-11 08:29:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kaleb KEITHLEY 2014-04-11 12:58:12 UTC

Description of problem:

argp-standalone is always built, even when not needed

Comment 1 Anand Avati 2014-04-11 13:02:42 UTC

REVIEW: http://review.gluster.org/7440 (configure: argp-standalone is always built, even when not needed) posted (#3) for review on master by Kaleb KEITHLEY (kkeithle)

Comment 2 Anand Avati 2014-04-13 21:34:43 UTC

COMMIT: http://review.gluster.org/7440 committed in master by Anand Avati (avati) 
------
commit 09d2dcac3a238cfe6bde1a7aed06facfa16caf20
Author: Kaleb S. KEITHLEY <kkeithle>
Date:   Thu Apr 10 14:43:47 2014 -0400

    configure: argp-standalone is always built, even when not needed
    
    This patch still configures argp, i.e. creates Makefile in
    /contrib/argp-standalone, for the `make dist`, but there's no reason
    to compile it when it's not going to be linked into anything.
    
    Change-Id: Id0fcb717b5821d8a4c176e6274339f46b3a4a249
    BUG: 1086773
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle>
    Reviewed-on: http://review.gluster.org/7440
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Harshavardhana <harsha>
    Reviewed-by: Niels de Vos <ndevos>
    Reviewed-by: Anand Avati <avati>

Comment 3 Niels de Vos 2014-09-22 12:37:56 UTC

A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 4 Niels de Vos 2014-11-11 08:29:51 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users