Bug 597460 - m4 won't compile from src.rpm on RHEL6 BETA
m4 won't compile from src.rpm on RHEL6 BETA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: m4 (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Vitezslav Crhonek
Michal Nowak
Depends On:
  Show dependency treegraph
Reported: 2010-05-28 21:52 EDT by Todd Rinaldo
Modified: 2013-03-07 21:10 EST (History)
4 users (show)

See Also:
Fixed In Version: m4-1.4.13-5.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-10 16:08:46 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 Todd Rinaldo 2010-05-28 21:52:08 EDT
Description of problem:

When I try to compile m4 from source, I get an error from patches.c about S_ISDIR not being defined during linking.

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

How reproducible:

Steps to Reproduce:
1. rpmbuild --rebuild ftp://ftp.redhat.com/redhat/rhel/beta/6/source/SRPMS/m4-1.4.13-4.1.el6.src.rpm
Actual results:

Errors during linking about S_ISDIR not being defined.

Expected results:

m4 should build

Additional info:

The M4 bugs mailing list acknowledges the problem and modified my suggested fix. This fix should go into RHEL6 and/or the new version should go in.


Shouldn't m4 be re-built from source against RHEL 6's libc?
Comment 2 RHEL Product and Program Management 2010-06-02 10:45:36 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
Comment 5 releng-rhel@redhat.com 2010-11-10 16:08:46 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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