Bug 90617

Summary: New perl modules fail to make when using CPAN
Product: [Retired] Red Hat Linux Reporter: Adam H. Pendleton <fmonkey>
Component: perlAssignee: Chip Turner <cturner>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:52:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Adam H. Pendleton 2003-05-11 05:00:19 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4b)

Description of problem:
When using CPAN to install new perl modules, the 'make' command fails every time
with a "Makefile:XX: *** missing separator.  Stop." where XX is a line number. 
The following *always* appears at that line, regardless of module:


The ** line is the line in question (it does not appear in the file surrounded
by **'s).

perl -MCPAN -e shell
cpan> install CDB_File
Writing Makefile for CDB_File
Makefile:82: *** missing separator.  Stop.
  /usr/bin/make  -- NOT OK

This section of the Makefile seems to be generated by MakeMaker.  I could not
determine the cause of this problem, so I am reporting it as a bug since it
happens on *all* my RH 9 distributions, and I can't find CDB_File in a RPM.

Version-Release number of selected component (if applicable):
perl-5.8.0-88 perl-CPAN-1.61-88

How reproducible:

Steps to Reproduce:
1. perl -M CPAN -e shell
2. cpan> install CDB_File

Actual Results:  [snip]
Writing Makefile for CDB_File
Makefile:82: *** missing separator.  Stop.
  /usr/bin/make  -- NOT OK

Additional info:

Comment 1 Chip Turner 2003-05-12 15:07:07 UTC

*** This bug has been marked as a duplicate of 87682 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:52:58 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.