perl-help | 12 Jun 16:38 2007
Picon

confirm unsubscribe to perl <at> lists.mysql.com

To confirm that you would like

  gcdmp-msql-mysql-modules <at> m.gmane.org

removed from the perl mailing list, please click on
the following link:

  http://lists.mysql.com/u/perl/466eafcf76b891d4/gcdmp-msql-mysql-modules=m.gmane.org

This confirmation serves two purposes. First, it verifies that we are
able to get mail through to you. Second, it protects you in case
someone forges a subscription request in your name.

We haven't checked whether your address is currently on the mailing list.
To see what address you used to subscribe, look at the messages you are
receiving from the mailing list. Each message has your address hidden
inside its return path; for example, john <at> example.com receives messages
with return path: perl-return-≤number>-john=example.com <at> lists.mysql.com.

--- Administrative commands for the perl list ---

I can handle administrative requests automatically. Please
do not send them to the list address! Instead, send
your message to the correct command address:

For help and a description of available commands, send a message to:
   <perl-help <at> lists.mysql.com>

To subscribe to the list, send a message to:
   <perl-subscribe <at> lists.mysql.com>
(Continue reading)

perl-help | 12 Jun 16:38 2007
Picon

confirm unsubscribe to perl <at> lists.mysql.com

To confirm that you would like

  gcdmp-msql-mysql-modules <at> m.gmane.org

removed from the perl mailing list, please click on
the following link:

  http://lists.mysql.com/u/perl/466eafd9df7aa65b/gcdmp-msql-mysql-modules=m.gmane.org

This confirmation serves two purposes. First, it verifies that we are
able to get mail through to you. Second, it protects you in case
someone forges a subscription request in your name.

We haven't checked whether your address is currently on the mailing list.
To see what address you used to subscribe, look at the messages you are
receiving from the mailing list. Each message has your address hidden
inside its return path; for example, john <at> example.com receives messages
with return path: perl-return-≤number>-john=example.com <at> lists.mysql.com.

--- Administrative commands for the perl list ---

I can handle administrative requests automatically. Please
do not send them to the list address! Instead, send
your message to the correct command address:

For help and a description of available commands, send a message to:
   <perl-help <at> lists.mysql.com>

To subscribe to the list, send a message to:
   <perl-subscribe <at> lists.mysql.com>
(Continue reading)

Brian Xia | 21 Jun 22:55 2007

Got error when build DBD:mysql

Hi,

I am installing a very old version of DBD-mysql. The Perl version is 
5.005_03 built for sun4-solaris.  And it is hacked and rebuild from 
source so that the embedded Perl application was made.

I downloaded the oldest version I can find -- DBD-mysql-2.1012 and

followed the steps,

perl Makefile.PL
make

I got the following error message.
cc -c 
-I/project/software2/Mace/EPG/BrianXia/release/mace/lib/solaris/perl5/site_perl/auto/DBI 
-I/usr/local/include/mysql -DMULTIPLICITY -O    -DVERSION=\"2.1012\" 
-DXS_VERSION=\"2.1012\" -KPIC 
-I/project/software2/Mace/EPG/BrianXia/release/mace/lib/solaris/perl5/CORE  
mysql.c
"mysql.xs", line 19: warning: syntax error:  empty declaration
"mysql.xs", line 54: warning: argument #3 is incompatible with prototype:
        prototype: pointer to char : "./dbdimp.h", line 200
        argument : pointer to const char
"mysql.xs", line 93: warning: argument #3 is incompatible with prototype:
        prototype: pointer to char : "./dbdimp.h", line 200
        argument : pointer to const char
"mysql.xs", line 99: prototype mismatch: 1 arg passed, 2 expected
"mysql.xs", line 137: warning: argument #3 is incompatible with prototype:
        prototype: pointer to char : "./dbdimp.h", line 200
(Continue reading)

Jeff Nokes | 28 Jun 04:15 2007
Picon

DBD::mysql connect dying with "Can't initialize character set latin1"

Hi,
I have a project where I have multiple mod_perl hosts that need to connect to a MySQL 5.0.37 instance.  The
mod_perl app runs on RedHat 7.2, and the MySQL server runs on Solaris 10.

I chose to use a pre-compiled linux binary package from MySQL, that comes with all related libraries,
header files, etc.  I successfully built my DBD::mysql using the pre-compiled package libraries, but am
having difficulties connecting to the server.  I'm seeing the following error when I try to connect:

   Character set 'latin1' is not a compiled character set and is not specified in the
'/usr/local/mysql/share/mysql/charsets/Index.xml' file
   DBI connect('database=blah blah) failed: Can't initialize character set latin1 (path: /usr/local/mysql/share/mysql/charsets/)

I'm assuming this path is something that is dictated via the pre-built package I'm using.  I have this
package on a single development host to do the linking of DBD::mysql where that path does exist, but not on
my other dev/QA or prod hosts.

I dug around a bit on Google and  in the DBI, DBD::mysql and MySQL docs, and came across this:
   http://dev.mysql.com/doc/refman/5.0/en/cannot-initialize-character-set.html

I'm wondering if there is a way that I can tell the DBD::mysql client library an arbitrary path to those
charset files, or if there is a way to inlcude an arbitrary path or the charset files themselves as part of
the process that generates .so?  Am I even barking up the right tree?

I also have some design constraints in that I cannot install this version of MySQL on my mod_perl hosts. 
Operational policy dictates that all code, libraries, configurations, etc. that I need, must be
deployed in the build as a self-contained entity.  I should also mention that the schema I'm connecting to
is all in UTF8.

If anyone has any suggestions, I'd love to hear them.  And thanks in advance for any assistance you can offer.

(Continue reading)

perl | 28 Jun 16:53 2007

mean-spirited cigar

dhtk xwsrvifssjn weravdy ytbjsjw tcpc qhwdu

Gmane