Bug 2599 - m4 rpm fails to 'provide' m4
Summary: m4 rpm fails to 'provide' m4
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: m4
Version: 6.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-05-06 13:50 UTC by R P Herrold
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 1999-05-06 15:26:51 UTC
Embargoed:


Attachments (Terms of Use)

Description R P Herrold 1999-05-06 13:50:04 UTC
The new m4 package build does not 'provide' an 'acceptible
'm4' for "rpm -ba specfile" rebuilds:
---------------------------------------------------------
[root@new ERRORS]# tail autofs.errors
+ /bin/chmod -Rf a+rX,g-w,o-w .
+ echo Patch #0:
+ patch -p1 -b --suffix .rh -s
+ exit 0
+ umask 022
+ cd /usr/src/redhat/BUILD
+ cd autofs-3.1.3
+ autoconf
Autoconf requires GNU m4 1.1 or later
Bad exit status from /var/tmp/rpm-tmp.88794 (%build)
[root@new ERRORS]# rpm -q --queryformat
"%{name}\t${provide}\n" m4
m4
[root@new ERRORS]# rpm -qi m4
Name        : m4                           Relocations: (not
relocateable)
Version     : 1.4                               Vendor: Red
Hat Software
Release     : 12                            Build Date: Sun
Mar 21 20:59:01 1999
Install date: Wed May  5 23:04:16 1999      Build Host:
porky.devel.redhat.com
Group       : Applications/Text             Source RPM:
m4-1.4-12.src.rpm
Size        : 122899                           License: GPL
Packager    : Red Hat Software
<http://developer.redhat.com/bugzilla/>
Summary     : The GNU macro processor.

Comment 1 Jeff Johnson 1999-05-06 15:26:59 UTC
This problem has nothing to do with m4. And autofs builds perfectly
on my Red Hat 6.0 sparc system.

You will need to look at autoconf to find out what it is complaining
about so that you can find out what is wrong on you system


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