Front page | perl.perl5.porters |
Postings from December 2008
On Mon, 15 Dec 2008, VIKAS BABAJIYAVAR wrote:
> # New Ticket Created by VIKAS BABAJIYAVAR
> # Please include the string: [perl #61372]
> # in the subject line of all future correspondence about this issue.
> # <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=61372 >
>
>
>
> Sir,
>
> My name is Vikas Babajiyavar.
> I wish to learn Perl programming on System76 Laptop.
> I am getting following error in Ubuntu Linux 8.10 operating system for Perl 5.10 version.
>
> Looking for extensions...
> A number of extensions are supplied with perl5. You may choose to
> compile these extensions for dynamic loading (the default), compile
> them into the perl5 executable (static loading), or not include
> them at all. Answer "none" to include no extensions.
> Note that DynaLoader is always built and need not be mentioned here.
>
> NOTICE: Your previous config.sh list may be incorrect.
> The extensions now available to you are
> B Compress/Raw/Zlib Cwd Data/Dumper Devel/DProf Devel/PPPort Devel/Peek Digest/MD5 Digest/SHA Encode Fcntl File/Glob Filter/Util/Call Hash/Util I18N/Langinfo IO IPC/SysV List/Util MIME/Base64 Math/BigInt/FastCalc Opcode POSIX PerlIO/encoding PerlIO/scalar PerlIO/via SDBM_File Socket Storable Sys/Hostname Sys/Syslog Text/Soundex Time/HiRes Time/Piece Unicode/Normalize XS/APItest XS/Typemap attrs re threads threads/shared Hash/Util/FieldHash
>
> What extensions do you wish to load dynamically? [ ] none
> What extensions do you wish to load statically? [?] ?
> WARNING: Extensions DB_File or *DBM_File, Fcntl, and IO not configured.
> WARNING: The Perl you are building will be quite crippled.
The problem seems to be that you are using an old config.sh from
somewhere. The key line is this one:
NOTICE: Your previous config.sh list may be incorrect.
Configure outputs that line when it detects your are using a version of
config.sh generated previously (perhaps from an old perl versioon). The
simplest fix may be to start with a fresh copy of the distribution, but
without knowing where that old config.sh came from and why you were trying
to use an old config.sh, I can't guess what you were trying to do.
--
Andy Dougherty doughera@lafayette.edu
Thread Previous
|
Thread Next