Bug 1032382 - autogen.sh warnings with automake-1.14
Summary: autogen.sh warnings with automake-1.14
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: GlusterFS
Classification: Community
Component: build
Version: mainline
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-20 04:55 UTC by Kaushal
Modified: 2019-07-05 07:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-05 07:26:13 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 6306 0 None Abandoned Set subdir-objects automake option in configure.ac 2019-07-18 13:16:16 UTC

Description Kaushal 2013-11-20 04:55:36 UTC
With automake-1.14, we get a lot of warning regarding subdir-objects on running autogen.sh.

Comment 1 Kaushal 2013-11-20 04:58:42 UTC
Patch under review at http://review.gluster.org/6306

Comment 2 Niels de Vos 2015-02-02 11:56:36 UTC
Hi Kaushal,

the patch is not sufficient, it will fail to build. Some additional changes are needed. Is this something you can look into, or should I have a go at it?

Thanks,
Niels

Comment 3 Kaushal 2015-12-04 07:37:55 UTC
I'll take a look at this sometime soon. autogen.sh generates even more warnings/errors now.

Comment 4 Mike McCune 2016-03-28 22:51:39 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 5 Worker Ant 2019-05-07 13:48:10 UTC
REVIEW: https://review.gluster.org/6306 (Set subdir-objects automake option in configure.ac) posted (#2) for review on master by Amar Tumballi

Comment 6 Amar Tumballi 2019-07-05 07:26:13 UTC
Not worked on in last 4 years, and the patch refresh also didn't get any comments. Marking as DEFERRED to represent current state.


Note You need to log in before you can comment on or make changes to this bug.