Hello Craig,

>At 6:42 PM +0930 6/15/03, Jeremy Begg wrote:
>>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.
>
>Yes, that's what it's for, but it only creates that if you run the
>INSTALL target.

OK, that makes sense.

>>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.
>
>Did you install them after building them?

Yes, I did the standard

    perl makefile.pl
    mms
    mms test
    mms install

for each of them (except no 'test' for ShowTable because the release notes
say it's broken).

>>   %LINK-W-NUDFSYMS, 55 undefined symbols:
>
>That's basically the whole Perl API, or all of it that DBD::MySQL
>appears to make use of.  Is the logical name PERLSHR defined?  Are
>you quite sure you've resolved all problems upstream from the link
>failure?  Since the link is one of the last things that happens,
>something going wrong in a previous step could well be the root issue.

Hmmm. I'll have to try a bit harder to work out what's going wrong.
I noticed that there's many references to a symbol "$verbose" in the
install script which causes it to produce diagnostics.  How do I
activate that from the 'mms install' command?

>If you switched where PERL_ROOT points to in mid-stream, be sure to
>make the REALCLEAN target and rerun the Makefile.PL.

I'll try that too.  It's quite possible I did redefine it after starting.

>Are you using Jean-Fran�ois Pi�ronne's new MySQL port?  I'd be
>interested to hear how you fare with it as I haven't heard of
>DBD::MySQL being used on VMS before.

Yes, that's the one.  He and I have been working on refining his port and
at my suggestion he's produced a nice PCSI kit for those who don't want to
(or can't) build from sources.

Regards,

        Jeremy Begg

Reply via email to