Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 77370 - @INC is not setup correctly in perl-5.8.0-55 (redhat 8.0)
Summary: @INC is not setup correctly in perl-5.8.0-55 (redhat 8.0)
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: perl
Version: 8.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Chip Turner
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2002-11-05 22:14 UTC by Craig Kelley
Modified: 2007-04-18 16:48 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2002-11-05 22:14:52 UTC

Attachments (Terms of Use)

Description Craig Kelley 2002-11-05 22:14:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
Use CPAN to install a new perl module.  It will put it in the following path:


but this path is not in @INC; so none of the custom modules can actually be used.

Version-Release number of selected component (if applicable): perl-5.8.0-55 and
Redhat 8.0

How reproducible:

Steps to Reproduce:
(as root)
perl -MCPAN -e shell;
CPAN> install Xmms  (be certain that both xmms and xmms-devel are installed)

 [wait and then exit CPAN]

Actual Results:  $ perl -MXmms
Can't locate in @INC (@INC contains:
/usr/local/lib/perl5/5.6.1/i686-linux /usr/local/lib/perl5/5.6.1
/usr/local/lib/perl5/site_perl/5.6.1 /usr/local/lib/perl5/site_perl
/usr/lib/perl5/5.6.1/i686-linux /usr/lib/perl5/5.6.1 /usr/lib/perl5 .).

Expected Results:  No path error

Additional info:

Send email if you have any questions.  This pretty much makes CPAN useless, and
it works just fine with a normal installation of perl.

Comment 1 Craig Kelley 2002-11-05 23:51:11 UTC
Ahh, perl-5.8.0-55 wasn't compiled with thread support, so of course this won't

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