Hi,
I'm running Perl 5.8.0 on OpenVMS Alpha 7.3 and I'm trying to build support
for MySQL. I've downloaded the following kits from CPAN:
DATA-SHOWTABLE-3_3
DBD-MYSQL-2_1027
DBI-1_37
I noticed that when I built Perl 5.8.0 a month or so ago it created a
second, parallel, directory tree [PERL-5_8_0_ROOT] which I assumed at
the time was meant to be the place you point PERL_ROOT to for general
users. But when I tried to add the Net::LDAP module I found it failed
badly because [PERL-5_8_0_ROOT] didn't have MINIPERL.EXE and lots of
other stuff required for adding Perl modules. So I learned to define
PERL_ROOT to point to the "full" Perl 5.8.0 kit directory before building
any add-on modules.
Is this expected behaviour? If so, what's the rationale?
Today's problem is that I'm trying to build DBD::mysql. The installation
instructions specified I should start by building the DBI module and also
Data::ShowTable, both of which I downloaded from CPAN and seemed to go OK.
When building DBD::mysql I found a number of problems, mainly due to
various assumptions made by the module's writer, but the killer in the end
came when the build procedure tried to link the final shareable image,
[.BLIB.ARCH.AUTO.DBD.MYSQL]PL_DBD__MYSQL.EXE. Lots of undefined symbols:
%LINK-W-NUDFSYMS, 55 undefined symbols:
%LINK-I-UDFSYM, PL_Sv
%LINK-I-UDFSYM, PL_Xpv
%LINK-I-UDFSYM, PL_curpad
%LINK-I-UDFSYM, PL_dirty
%LINK-I-UDFSYM, PL_markstack_max
%LINK-I-UDFSYM, PL_markstack_ptr
%LINK-I-UDFSYM, PL_op
%LINK-I-UDFSYM, PL_perl_destruct_level
%LINK-I-UDFSYM, PL_stack_base
%LINK-I-UDFSYM, PL_stack_max
%LINK-I-UDFSYM, PL_stack_sp
%LINK-I-UDFSYM, PL_sv_no
%LINK-I-UDFSYM, PL_sv_undef
%LINK-I-UDFSYM, PL_sv_yes
%LINK-I-UDFSYM, PerlIO_printf
%LINK-I-UDFSYM, Perl_av_extend
%LINK-I-UDFSYM, Perl_av_make
%LINK-I-UDFSYM, Perl_av_push
%LINK-I-UDFSYM, Perl_call_method
%LINK-I-UDFSYM, Perl_croak
%LINK-I-UDFSYM, Perl_dowantarray
%LINK-I-UDFSYM, Perl_form
%LINK-I-UDFSYM, Perl_get_sv
%LINK-I-UDFSYM, Perl_hv_fetch
%LINK-I-UDFSYM, Perl_hv_store
%LINK-I-UDFSYM, Perl_markstack_grow
%LINK-I-UDFSYM, Perl_mg_get
%LINK-I-UDFSYM, Perl_mg_set
%LINK-I-UDFSYM, Perl_mg_size
%LINK-I-UDFSYM, Perl_newAV
%LINK-I-UDFSYM, Perl_newHV
%LINK-I-UDFSYM, Perl_newRV
%LINK-I-UDFSYM, Perl_newRV_noinc
%LINK-I-UDFSYM, Perl_newSV
%LINK-I-UDFSYM, Perl_newSViv
%LINK-I-UDFSYM, Perl_newSVpv
%LINK-I-UDFSYM, Perl_newSVpvn
%LINK-I-UDFSYM, Perl_newXS
%LINK-I-UDFSYM, Perl_safesysfree
%LINK-I-UDFSYM, Perl_safesysmalloc
%LINK-I-UDFSYM, Perl_stack_grow
%LINK-I-UDFSYM, Perl_sv_2bool
%LINK-I-UDFSYM, Perl_sv_2iv
%LINK-I-UDFSYM, Perl_sv_2mortal
%LINK-I-UDFSYM, Perl_sv_2pv_flags
%LINK-I-UDFSYM, Perl_sv_2pv_nolen
%LINK-I-UDFSYM, Perl_sv_backoff
%LINK-I-UDFSYM, Perl_sv_free
%LINK-I-UDFSYM, Perl_sv_newmortal
%LINK-I-UDFSYM, Perl_sv_setiv
%LINK-I-UDFSYM, Perl_sv_setnv
%LINK-I-UDFSYM, Perl_sv_setpv
%LINK-I-UDFSYM, Perl_sv_setpvn
%LINK-I-UDFSYM, Perl_warn
%LINK-I-UDFSYM, BOOT_DBD__MYSQL
%LINK-W-USEUNDEFSYMV, undefined symbol BOOT_DBD__MYSQL referenced
in symbol vector option
Either the DBD::mysql build procedure is making a lot of wrong assumptions,
or I've got something very broken here! Any help would be appreciated.
Thanks,
Jeremy Begg
+---------------------------------------------------------+
| VSM Software Services Pty. Ltd. |
| http://www.vsm.com.au/ |
| "OpenVMS Systems Management & Programming" |
|---------------------------------------------------------|
| P.O.Box 402, Walkerville, | E-Mail: [EMAIL PROTECTED] |
| South Australia 5081 | Phone: +61 8 8221 5188 |
|---------------------------| Mobile: 0414 422 947 |
| A.C.N. 068 409 156 | FAX: +61 8 8221 7199 |
+---------------------------------------------------------+
