Error: "Not is not intended for this build of Perl (MSWin32-x86-m ulti-thread-5.8)"

I've tried to install DBD::mysql via PPM2, PPM3, and also by manually
downloading the the zip file and installing by PPM2.

Essentially, I get the same error message, saying that I can't install the
package on my build of Perl. I just installed ActivePerl 5.8 on Windows 2000
Server.

I searched the lists archives but could not find anyone yet with this
problem. So far, I have not had any trouble installing other packages.

_______________
Example of error message when installing manually via PPM2:

Installing package 'DBD-Mysql.ppd'...
Error installing package 'DBD-Mysql.ppd': Read a PPD for 'DBD-Mysql.ppd',
but it
is not intended for this build of Perl (MSWin32-x86-multi-thread-5.8)
_______________

This is my first install of Perl so I hope I'm not asking an FAQ.

Thanks in advance. Leo.

---------------------------------------------------------------------
Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before
posting. To request this thread, e-mail msql-mysql-modules-thread1996 <at> lists.mysql.com

To unsubscribe, send a message to the address shown in the
List-Unsubscribe header of this message. If you cannot see it,
e-mail msql-mysql-modules-unsubscribe <at> lists.mysql.com instead.

RE: Error: "Not is not intended for this build of Perl (MSWin32-x86-multi-thread-5.8)"

I got ppd from http://theoryx5.uwinnipeg.ca/ppms .
c:> ppm install http://theoryx5.uwinnipeg.ca/ppms/dbd-mysql.ppd should do
it.
And make sure that libmySQL.dll is in your path or where PERL is expecting
find. I copied to Perl directory/site/lib/auto/DBD/mysql.

HTH,

Howard

-----Original Message-----
From: Leo Lui [mailto:LeoLui <at> syscon.bc.ca]
Sent: January 2, 2003 4:44 PM
To: 'msql-mysql-modules <at> lists.mysql.com'
Subject: Error: "Not is not intended for this build of Perl
(MSWin32-x86-multi-thread-5.8)"

I've tried to install DBD::mysql via PPM2, PPM3, and also by manually
downloading the the zip file and installing by PPM2.

Essentially, I get the same error message, saying that I can't install the
package on my build of Perl. I just installed ActivePerl 5.8 on Windows 2000
Server.

I searched the lists archives but could not find anyone yet with this
problem. So far, I have not had any trouble installing other packages.

_______________
Example of error message when installing manually via PPM2:

Mem leak upon recovering after a disconnect

Hello,

In our mod_perl app we came across this rather nasty memory leak. I 
assume it is from DBD::mysql judging from the source, but if it's a DBI 
thing I can take it to that list.

This loop leaks at least a page of memory per iteration:

for my $i (1..1000) {
	my $dbh = DBI->connect(...);
	$dbh->disconnect();
	$dbh->do(something);
	sleep(1);
}

A small 4kb per iteration isn't the limit to how bad this leak is, we 
saw multiple megabytes per iteration leak in our full production setup. 
It is easy to workaround once we found the problem, we just check the 
Active flag before we do anything. Finding the problem took quite 
awhile though 

I understand that the above construct is dubious. There is a good 
explanation I won't get into as to how it came about. I'm not 
necessarily asking for the leak to get fixed, but if it doesn't get 
fixed I think the above should error out or give a warning.

I'll be happy to work up a patch to fix the leak or add a warning if 
someone could point me at the right places in the source to dive in, I 
didn't have much luck finding the right spot to start my attack.

Re: Mem leak upon recovering after a disconnect

Zitiere John Heitmann <JHeitmann <at> CombineNet.com>:

> for my $i (1..1000) {
> 	my $dbh = DBI->connect(...);
> 	$dbh->disconnect();
> 	$dbh->do(something);
> 	sleep(1);
> }

I do get you right, that the problem is caused because you
attempt to use a closed connection?

> It is easy to workaround once we found the problem, we just check the 
> Active flag before we do anything. Finding the problem took quite 
> awhile though 

By that you mean that you omit using the closed connection?

> I understand that the above construct is dubious.

It is not what I would have expected the users to do. 
Question: What happens, if you set the RaiseError flag and trap
the exception in the loop? (Using RaiseError is definitely
recommended.) Does that help?

Regards,

Jochen

Re: Mem leak upon recovering after a disconnect

On Friday, January 10, 2003, at 05:07  AM, Jochen Wiedmann wrote:

>
> Zitiere John Heitmann <JHeitmann <at> CombineNet.com>:
>
>> for my $i (1..1000) {
>> 	my $dbh = DBI->connect(...);
>> 	$dbh->disconnect();
>> 	$dbh->do(something);
>> 	sleep(1);
>> }
>
> I do get you right, that the problem is caused because you
> attempt to use a closed connection?

Exactly.

>
>> It is easy to workaround once we found the problem, we just check the
>> Active flag before we do anything. Finding the problem took quite
>> awhile though 
>
> By that you mean that you omit using the closed connection?

Right, so here's our current fix (since in our full example we can 
never be sure if 3rd party code has closed the connection):

for my $i (1..1000) {
	my $dbh = DBI->connect(...);

Re: Sample

Attached file:

---------------------------------------------------------------------
Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before
posting. To request this thread, e-mail msql-mysql-modules-thread2002 <at> lists.mysql.com

To unsubscribe, send a message to the address shown in the
List-Unsubscribe header of this message. If you cannot see it,
e-mail msql-mysql-modules-unsubscribe <at> lists.mysql.com instead.

Re: Document

Attached file:

---------------------------------------------------------------------
Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before
posting. To request this thread, e-mail msql-mysql-modules-thread2001 <at> lists.mysql.com

To unsubscribe, send a message to the address shown in the
List-Unsubscribe header of this message. If you cannot see it,
e-mail msql-mysql-modules-unsubscribe <at> lists.mysql.com instead.

âÍ¡ÒÈ·Ò§¸ØÃСԨ 17/1/2003 3:02:32

Dear msql-mysql-modules ,

ÊÅÐàÇÅÒÊÑ¡¹Ô´à¾×èͤسáÅФ¹·Õè¤ÃÑ¡

www.geocities.com/healthclub999/hc076

$ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $

"¢ÍÍÀÑ ËÒ¡¢éͤÇÒÁ¹Õé¶Ù¡Êè§ä»Âѧ¤Ø³â´ÂºÑ§àÍÔ­ 
ËÒ¡¤Ø³µéͧ¡ÒÃãËéÃÒª×èͶ١źÍÍ¡¡ÃسÒÊè§ email ¢Í§¤Ø³ÁÒ·Õè
thaiget <at> thaimail.com  â´Âà¢Õ¹ËÑÇ¢éÍÇèÒ    Unsubscribe"

---------------------------------------------------------------------
Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before
posting. To request this thread, e-mail msql-mysql-modules-thread2003 <at> lists.mysql.com

To unsubscribe, send a message to the address shown in the
List-Unsubscribe header of this message. If you cannot see it,
e-mail msql-mysql-modules-unsubscribe <at> lists.mysql.com instead.

download DBD::mysql using PPM 3

Hi,

The instructions you give for Binary Installation of DBD::mysql to
Windows using PPM 3 do not work.
There is no "rep 2" command (the third command in your instructions).

Yu Tang
(630)252-4796
yutang <at> anl.gov

Re: download DBD::mysql using PPM 3

On Tue, 21 Jan 2003, Yu Tang wrote:

> Hi,
>  
> The instructions you give for Binary Installation of DBD::mysql to
> Windows using PPM 3 do not work.
> There is no "rep 2" command (the third command in your instructions).

You can either install DBD-mysql directly as
  C:\> ppm install
     http://theoryx5.uwinnipeg.ca/ppmpackages/DBD-mysql.ppd
for ActivePerl builds 6xx, or as
  C:\> ppm install
     http://theoryx5.uwinnipeg.ca/ppms/DBD-mysql.ppd
for build 8xx. Alternatively, within the ppm shell,
set the repository to
  http://theoryx5.uwinnipeg.ca/cgi-bin/ppmserver?urn:/PPMServer
for 6xx, or
  http://theoryx5.uwinnipeg.ca/cgi-bin/ppmserver?urn:/PPMServer58
for 8xx. See the help utility within the ppm shell for
how to set the repository.

If you get a problem about a missing library when using these,
try adding the path to the mysql dlls (eg, C:\mysql\lib\opt,
where libmySQL.dll lives) to your PATH environment variable.

These packages were compiled against mysql-3.23.51 - I
believe they won't work with mysql-4.

--

--