Bug 1050055 - Add -vi to autoreconf in libdv spec file
Summary: Add -vi to autoreconf in libdv spec file
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: libdv
Version: 22
Hardware: ppc64le
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: John Feeney
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-08 16:40 UTC by Brent Baude
Modified: 2016-07-19 19:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 19:28:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Brent Baude 2014-01-08 16:40:36 UTC
Description of problem:

In order for libdv to build on the ppc64le arch, the following trivial change is needed. Would you consider this for libdv in rawhide?

diff --git a/libdv.spec b/libdv.spec
index efd5022..53b3496 100644
--- a/libdv.spec
+++ b/libdv.spec
@@ -56,7 +56,7 @@ This package contains development files for libdv.
 # Required for libtool 2.2
 libtoolize
 # Required for the gtk2 patch
-autoreconf
+autoreconf -vi
 
 %build
 %configure --with-pic

Comment 2 Jaroslav Reznik 2015-03-03 15:22:40 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 3 Fedora End Of Life 2016-07-19 19:28:31 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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