Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 88341

Summary: CPAN compile results in bogus Makefile
Product: [Retired] Red Hat Linux Reporter: John Simpson <jms1>
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: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:52:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Makefile generated by "perl Makefile.pl" none

Description John Simpson 2003-04-09 04:36:51 UTC
Description of problem:
Trying to compile certain CPAN modules (so far CDB_File and updated CPAN) from
source generates an invalid Makefile, containing random four-line chunks of
Config.pm instead of single values.

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

How reproducible:
try to build CPAN CDB_File module

Steps to Reproduce:
1. wget http://search.cpan.org/CPAN/authors/id/M/MS/MSERGEANT/CDB_File-0.93.tar.gz
2. tar xvzf CDB_File-0.93.tar.gz
3. cd CDB_File-0.93
4. perl Makefile.PL
5. make
    
Actual results:
Makefile:82: *** missing separator.  Stop.

Expected results:
module builds correctly

Additional info:
same thing happened under the 8.1 beta, but module builds correctly under 7.3
and 8.0.

Comment 1 John Simpson 2003-04-09 04:39:25 UTC
Created attachment 91026 [details]
Makefile generated by "perl Makefile.pl"

Comment 2 John Simpson 2003-04-09 05:51:43 UTC
Found bug #84268, tried with LANG=C and with LANG totally unset. In both cases
it builds a valid makefile, and "make" works, but "make test" comes back with
errors. I am working with the module's author for a fix.

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

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