-----Original Message-----
From: Mark Buckle
Sent: 04 February 2002 13:41
To: 'Berger, Daniel'; 'tzonekev'; [EMAIL PROTECTED]
Subject: RE: ActivePerl & DBI - can't build DBI1.20
I've tried building DBI-1.20 on NT with VC++ 5, and come up with the
following error (I've mapped copy to cp BTW) :-
$ perl Makefile.PL
*** You are using a perl with experimental threading enabled!
*** You should be aware that using multiple threads is unstable
*** are should NOT be done in production environments.
DBI thread mutex protection is enabled
*** Note:
The optional PlRPC-modules (RPC::PlServer etc) are not installed.
If you want to use the DBD::Proxy driver and DBI::ProxyServer
modules, then you'll need to install the RPC::PlServer, RPC::PlClient,
Storable and Net::Daemon modules. The CPAN Bundle::DBI may help you.
You can install them any time after installing the DBI.
You do *not* need these modules for typical DBI usage.
Optional modules are available from any CPAN mirror, in particular
http://www.perl.com/CPAN/modules/by-module
http://www.perl.org/CPAN/modules/by-module
ftp://ftp.funet.fi/pub/languages/perl/CPAN/modules/by-module
Checking if your kit is complete...
Looks good
Remember to actually *read* the README file!
Use 'make' to build the software (dmake or nmake on Windows).
Then 'make test' to execute self tests.
Then 'make install' to install the DBI and then delete this working
directory before unpacking and building any DBD::* drivers.
Windows users need to use the correct make command.
That may be nmake or dmake depending on which Perl you are using.
If using the Win32 ActiveState build then it is recommended that you
use the ppm utility to fetch and install a prebuilt DBI instead.
Writing Makefile for DBI
$ nmake
Microsoft (R) Program Maintenance Utility Version 1.62.7022
Copyright (C) Microsoft Corp 1988-1997. All rights reserved.
cp DBIXS.h blib\arch\auto\DBI/DBIXS.h
cp lib/DBD/NullP.pm blib\lib\DBD\NullP.pm
cp dbipport.h blib\arch\auto\DBI/dbipport.h
cp lib/DBI/Format.pm blib\lib\DBI\Format.pm
cp dbd_xsh.h blib\arch\auto\DBI/dbd_xsh.h
cp lib/DBI/Shell.pm blib\lib\DBI\Shell.pm
cp lib/DBI/FAQ.pm blib\lib\DBI\FAQ.pm
cp DBI.pm blib\lib\DBI.pm
cp lib/DBD/ExampleP.pm blib\lib\DBD\ExampleP.pm
cp lib/Bundle/DBI.pm blib\lib\Bundle\DBI.pm
cp lib/Win32/DBIODBC.pm blib\lib\Win32\DBIODBC.pm
cp lib/DBI/W32ODBC.pm blib\lib\DBI\W32ODBC.pm
cp lib/DBI/DBD.pm blib\lib\DBI\DBD.pm
cp lib/DBD/Proxy.pm blib\lib\DBD\Proxy.pm
cp lib/DBI/ProxyServer.pm blib\lib\DBI\ProxyServer.pm
cp dbi_sql.h blib\arch\auto\DBI/dbi_sql.h
cp Driver.xst blib\arch\auto\DBI/Driver.xst
cp lib/DBD/Sponge.pm blib\lib\DBD\Sponge.pm
C:\perl\bin\perl.exe -p -e "s/~DRIVER~/Perl/g" <
blib\arch\auto\DBI/Driver.xst > Perl.xsi
C:\perl\bin\perl.exe -IC:\Perl\lib -IC:\Perl\lib
C:\Perl\lib\ExtUtils/xsubpp -typemap C:\Perl\lib\ExtUtils\typemap Perl.xs >
Perl.xsc && C:\perl\bin\perl.exe -IC:\Perl\lib -IC:\Perl\lib
-MExtUtils::Command -e mv Perl.xsc Perl.c
cl -c -nologo -O1 -MD -DNDEBUG -DWIN32 -D_CONSOLE -DNO_STRICT
-DHAVE_DES_FCRYPT -DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS
-DPERL_MSVCRT_READFIX -O1 -MD -DNDEBUG -DVERSION=\"1.20\"
-DXS_VERSION=\"1.20\" -IC:\Perl\lib\CORE Perl.c
NMAKE : fatal error U1077: 'cl' : return code '0x80'
Stop.
$
-----Original Message-----
From: Berger, Daniel [mailto:[EMAIL PROTECTED]]
Sent: 05 October 2001 15:25
To: 'tzonekev'; [EMAIL PROTECTED]
Subject: RE: ActivePerl & DBI
Mr. Bunce (or someone) will have generate a new .ppd file for version 1.20
in order for you to use PPM.
In the meantime, you can either do:
1) perl -MCPAN -e shell; install DBI
or
2) perl Makefile.PL; make; make test; make install (replace make with nmake
if MS Windoze)
Regards,
Mr. Sunblade
-----Original Message-----
From: tzonekev [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 04, 2001 4:32 PM
To: [EMAIL PROTECTED]
Subject: ActivePerl & DBI
Can anyone please help in upgrading active state perl DBI module from
ver1.14, readily available on the ActiveState repository, to version
1.20, the current one, found on many CPAN sites
Kevin Pickering
Planet Telecom
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
**********************************************************************