Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 229281 - FutureFeature: Requesting version 1.10
FutureFeature: Requesting version 1.10
Product: Fedora
Classification: Fedora
Component: automake (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Karsten Hopp
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2007-02-19 16:55 EST by Debarshi Ray
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-03-02 07:44:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Debarshi Ray 2007-02-19 16:55:28 EST
Description of problem:
This is to request you to kindly make version 1.10 of Automake available for
Fedora Core 5.

Version-Release number of selected component (if applicable):
The current version of Automake is 1.9.6.

I use automake (and autoconf) to generate the build infrastructure of a number
of programs I develop. GNU Parted is one such program. We are shifting to
Automake 1.10 (and Autoconf 2.61)  from now onwards to avoid having the bugs
that were fixed in the latest releases of Automake in the build infrastructure.
eg., if you use  automake-1.9.6, you end up distributing build infrastructure
that selects a version of "mkdir -p" that is not thread safe, and that may fail
when building with "make -j2".
Comment 1 Karsten Hopp 2007-03-02 07:44:54 EST
Automake-1.10 broke quite a few builds when it replaced automake-1.9.* in our 
As you seem to be familiar with the autofoo stuff, you should be able to 
rebuild the FC7(rawhide) package on your FC-6 system and cope with the 
resulting build problems. 
But I won't release a automake-1.10 for either FC-6 (bug #230609) or FC-6 as
not everyone is able to fix the resulting problems.

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