Bug 693497 - libnih-devel might cause failure in autoconf
Summary: libnih-devel might cause failure in autoconf
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libnih
Version: 6.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Lukáš Nykrýn
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
: 669059 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-04 19:58 UTC by Ondrej Moriš
Modified: 2017-12-06 11:39 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 11:39:50 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Ondrej Moriš 2011-04-04 19:58:27 UTC
Description of problem:

Hi, recently, we have discovered a strange problem while building nss-pam-ldapd package:

+ autoreconf -f -i 
configure.ac:23: error: m4_defn: undefined macro: _m4_divert_diversion
configure.ac:23: the top level 
autom4te: /usr/bin/m4 failed with exit status: 1 
aclocal: autom4te failed with exit status: 1 
autoreconf: aclocal failed with exit status: 1 
error: Bad exit status from /var/tmp/rpm-tmp.YUOpSt (%prep)

Finally, it has been found out that there is some interaction between configure script's use of AC_CANONICAL_TARGET and the libnih-devel package. And build succeeded when we have removed libnih-devel package.

I have absolutely no clue about what is happening here, but it seems like a bug to me.

Version-Release number of selected component (if applicable):

libnih-devel-1.0.1-6.el6

How reproducible:

Always.

Steps to Reproduce:

1. Install nss-pam-ldapd-0.7.5-5.el6 source rpm.
2. Install libnih-devel.
3. rpmbuild -vv -bp ~/rpmbuild/SPECS/nss-pam-ldapd.spec 

Actual results:

+ autoreconf -f -i
configure.ac:23: error: m4_defn: undefined macro: _m4_divert_diversion
configure.ac:23: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
aclocal: autom4te failed with exit status: 1
autoreconf: aclocal failed with exit status: 1
error: Bad exit status from /var/tmp/rpm-tmp.5cezSw (%prep)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.5cezSw (%prep)

Expected results:

+ autoreconf -f -i
+ exit 0

Comment 1 Petr Lautrbach 2011-04-05 12:04:34 UTC
Seems to be same issue as #669059 which should have been fixed in upstream libnih-1.0.2 version

Comment 4 RHEL Program Management 2011-07-06 00:06:47 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 5 Petr Lautrbach 2011-08-09 08:11:02 UTC
*** Bug 669059 has been marked as a duplicate of this bug. ***

Comment 6 Miroslav Vadkerti 2011-08-09 08:18:12 UTC
This can be tested via curl sanity test. It rebuilds curl with and also without installed libnih-devel pkg.

Comment 7 Kamil Dudka 2011-08-09 08:45:08 UTC
(In reply to comment #6)
> This can be tested via curl sanity test. It rebuilds curl with and also without
> installed libnih-devel pkg.

I am not sure how the test is implemented, but you need to use an old enough version of curl to trigger the failure.  Starting with curl-7.19.7-18.el6, there is a workaround for this bug in the curl package.

Comment 11 Suzanne Logcher 2012-02-14 23:08:20 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 12 RHEL Program Management 2013-10-14 01:07:45 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 17 Jan Kurik 2017-12-06 11:39:50 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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