Bug 117923 - Perl's spec is i386 specific
Summary: Perl's spec is i386 specific
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chip Turner
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-03-10 02:20 UTC by Nicholas Miell
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-03-10 03:41:23 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Fix the spec file (806 bytes, patch)
2004-03-10 02:29 UTC, Nicholas Miell
no flags Details | Diff
Fix the spec file (22.20 KB, patch)
2004-03-10 02:31 UTC, Nicholas Miell
no flags Details | Diff

Description Nicholas Miell 2004-03-10 02:20:40 UTC
this fragment from perl's %install is completely broken on all
non-i386 platforms:

pushd $RPM_BUILD_ROOT/%{_libdir}/perl5
for i in  5.8.0/i386-linux-thread-multi/CORE/
5.8.1/i386-linux-thread-multi/CORE/
5.8.2/i386-linux-thread-multi/CORE/; do
  mkdir -p $i
  pushd $i
  ln -s ../../../%{perlver}/i386-linux-thread-multi/CORE/libperl.so
libperl.so
  popd
done
popd

As a result, the latest errata perl and xchat for FC1 x86-64 conflict.

Comment 1 Nicholas Miell 2004-03-10 02:29:41 UTC
Created attachment 98414 [details]
Fix the spec file

Here's a patch for the spec, it's against perl-5.8.3-10.1.1.src.rpm

Comment 2 Nicholas Miell 2004-03-10 02:31:43 UTC
Created attachment 98415 [details]
Fix the spec file

New patch, this one doesn't twiddle the release

Comment 3 Chip Turner 2004-03-10 03:41:23 UTC
good catch.  fixed in cvs, should show up in rawhide.  used a different patch (one that 
used predefined rpm macros for arch, etc) but same idea.  should show up as 5.8.3-11


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