Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 3158 - Several perl binary packages not working
Several perl binary packages not working
Product: Red Hat Linux
Classification: Retired
Component: perl (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Crutcher Dunnavant
Depends On:
  Show dependency treegraph
Reported: 1999-05-30 13:44 EDT by ron
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-07-28 21:59:44 EDT
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 ron 1999-05-30 13:44:37 EDT
After installing RedHat 6.0 along with perl-5.00503-2,
several binary perl packages are not working.
In particular the DBI package - DBI-1.06-1 is having
problems.  When executing a script which uses this package I
get :
Can't load
'/usr/lib/perl5/site_perl//i386-linux/auto/DBI/DBI.so' for
module DBI:
undefined symbol: dirty at
/usr/lib/perl5/5.00503/i386-linux/DynaLoader.pm line 169.

 at /usr/lib/perl5/site_perl//DBI.pm line 168
BEGIN failed--compilation aborted at
/usr/lib/perl5/site_perl//DBI.pm line 168.
BEGIN failed--compilation aborted at ./dbTest line 3.

I have also had similar problems with the ePerl and embperl
I haven't tried installing from a source package yet.
Comment 1 shinta 1999-06-17 07:00:59 EDT
And 'pod2text' is not included.
please modify .spec file.
Comment 2 Cristian Gafton 1999-07-28 21:59:59 EDT
I would expect that a recompilation of the perl modules that are
causing these problems will fix things.

Please re-open if this is not the case.

As for the incomplete version of the .spec file, there is a new
version available in rawhide that should fix the spec file problem
(perl-5.00503-4 or later)

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