dbd::mysql::install.3

视频监控网络部分的协议ddns,的模块的实现代码,请大家大胆指正.

.Vb 1
\&  \-I/usr/include/mysql
.Ve
.Sp
On Windows the header files may be in C:\emysql\einclude and you might try
.Sp
.Vb 1
\&  \-IC:\emysql\einclude
.Ve
.Sp
The default flags are determined by running
.Sp
.Vb 1
\&  mysql_config \-\-cflags
.Ve
.Sp
More details on the C compiler flags can be found in the following
section. \*(L"Compiler flags\*(R".
.IP "libs" 4
.IX Item "libs"
This is a list of flags that you want to give to the linker
or loader. The most important flags are the locations and names
of additional libraries. For example, on Red Hat Linux your
MySQL client libraries are in /usr/lib/mysql and you might try
.Sp
.Vb 1
\&  \-L/usr/lib/mysql \-lmysqlclient \-lz
.Ve
.Sp
On Windows the libraries may be in C:\emysql\elib and
.Sp
.Vb 1
\&  \-LC:\emysql\elib \-lmysqlclient
.Ve
.Sp
might be a good choice. The default flags are determined by running
.Sp
.Vb 1
\&  mysql_config \-\-libs
.Ve
.Sp
More details on the linker flags can be found in a separate section.
\&\*(L"Linker flags\*(R".
.PP
If a switch is not present on the command line, then the
script \f(CW\*(C`mysql_config\*(C'\fR will be executed. This script comes
as part of the MySQL distribution. For example, to determine
the C compiler flags, we are executing
.PP
.Vb 2
\&  mysql_config \-\-cflags
\&  mysql_config \-\-libs
.Ve
.PP
If you want to configure your own settings for database name,
database user and so on, then you have to create a script with
the same name, that replies
.Sh "Compiler flags"
.IX Subsection "Compiler flags"
Note: the folling info about compiler and linker flags, you shouldn't have
to use these options because Makefile.PL is pretty good at utilising
mysql_config to get the flags that you need for a successful compile.
.PP
It is typically not so difficult to determine the appropriate
flags for the C compiler. The linker flags, which you find in
the next section, are another story.
.PP
The determination of the C compiler flags is usually left to
a configuration script called \fImysql_config\fR, which can be
invoked with
.PP
.Vb 1
\&  mysql_config \-\-cflags
.Ve
.PP
When doing so, it will emit a line with suggested C compiler
flags, for example like this:
.PP
.Vb 1
\&  \-L/usr/include/mysql
.Ve
.PP
The C compiler must find some header files. Header files have
the extension \f(CW\*(C`.h\*(C'\fR. MySQL header files are, for example,
\&\fImysql.h\fR and \fImysql_version.h\fR. In most cases the header
files are not installed by default. For example, on Windows
it is an installation option of the MySQL setup program
(Custom installation), whether the header files are installed
or not. On Red Hat Linux, you need to install an \s-1RPM\s0 archive
\&\fImysql-devel\fR or \fIMySQL-devel\fR.
.PP
If you know the location of the header files, then you will
need to add an option
.PP
.Vb 1
\&  \-L<header directory>
.Ve
.PP
to the C compiler flags, for example \f(CW\*(C`\-L/usr/include/mysql\*(C'\fR.
.Sh "Linker flags"
.IX Subsection "Linker flags"
Appropriate linker flags are the most common source of problems
while installing DBD::mysql. I will only give a rough overview,
you'll find more details in the troubleshooting section.
\&\*(L"\s-1KNOWN\s0 \s-1PROBLEMS\s0\*(R"
.PP
The determination of the C compiler flags is usually left to
a configuration script called \fImysql_config\fR, which can be
invoked with
.PP
.Vb 1
\&  mysql_config \-\-libs
.Ve
.PP
When doing so, it will emit a line with suggested C compiler
flags, for example like this:
.PP
.Vb 1
\&   \-L\*(Aq/usr/lib/mysql\*(Aq \-lmysqlclient \-lnsl \-lm   \-lz \-lcrypt
.Ve
.PP
The following items typically need to be configured for the
linker:
.IP "The mysqlclient library" 4
.IX Item "The mysqlclient library"
The MySQL client library comes as part of the MySQL distribution.
Depending on your system it may be a file called
.Sp
.Vb 4
\&  F<libmysqlclient.a>   statically linked library, Unix
\&  F<libmysqlclient.so>  dynamically linked library, Unix
\&  F<mysqlclient.lib>    statically linked library, Windows
\&  F<mysqlclient.dll>    dynamically linked library, Windows
.Ve
.Sp
or something similar.
.Sp
As in the case of the header files, the client library is typically
not installed by default. On Windows you will need to select them
while running the MySQL setup program (Custom installation). On
Red Hat Linux an \s-1RPM\s0 archive \fImysql-devel\fR or \fIMySQL-devel\fR must
be installed.
.Sp
The linker needs to know the location and name of the mysqlclient
library. This can be done by adding the flags
.Sp
.Vb 1
\&  \-L<lib directory> \-lmysqlclient
.Ve
.Sp
or by adding the complete path name. Examples:
.Sp
.Vb 2
\&  \-L/usr/lib/mysql \-lmysqlclient
\&  \-LC:\emysql\elib \-lmysqlclient
.Ve
.Sp
If you would like to use the static libraries (and there are
excellent reasons to do so), you need to create a separate
directory, copy the static libraries to that place and use
the \-L switch above to point to your new directory. For example:
.Sp
.Vb 7
\&  mkdir /tmp/mysql\-static
\&  cp /usr/lib/mysql/*.a /tmp/mysql\-static
\&  perl Makefile.PL \-\-libs="\-L/tmp/mysql\-static \-lmysqlclient"
\&  make
\&  make test
\&  make install
\&  rm \-rf /tmp/mysql\-static
.Ve
.IP "The gzip library" 4
.IX Item "The gzip library"
The MySQL client can use compression when talking to the MySQL
server, a nice feature when sending or receiving large texts over
a slow network.
.Sp
On Unix you typically find the appropriate file name by running
.Sp
.Vb 2
\&  ldconfig \-p | grep libz
\&  ldconfig \-p | grep libgz
.Ve
.Sp
Once you know the name (libz.a or libgz.a is best), just add it
to the list of linker flags. If this seems to be causing problem
you may also try to link without gzip libraries.
.SH "SPECIAL SYSTEMS"
.IX Header "SPECIAL SYSTEMS"
Below you find information on particular systems:
.Sh "Windows/CygWin"
.IX Subsection "Windows/CygWin"
If you are a user of Cygwin (the Redhat distribution) you already
know, it contains a nicely running perl 5.6.1, installation of
additional modules usually works as a charme via the standard
procedure of
.PP
.Vb 4
\&    perl makefile.PL
\&    make
\&    make test
\&    make install
.Ve
.PP
The Windows binary distribution of MySQL runs smoothly under Cygwin.
You can start/stop the server and use all Windows clients without problem.
But to install DBD::mysql you have to take a little special action.
.PP
Don't attempt to build DBD::mysql against either the MySQL Windows or
Linux/Unix \s-1BINARY\s0 distributions: neither will work!
.PP
You \s-1MUST\s0 compile the MySQL clients yourself under Cygwin, to get a
\&'libmysqlclient.a' compiled under Cygwin. Really! You'll only need
that library and the header files, you don't need any other client parts.
Continue to use the Windows binaries. And don't attempt (currently) to
build the MySQL Server part, it is unneccessary, as MySQL \s-1AB\s0 does an
excellent job to deliver optimized binaries for the mainstream
operating systems, and it is told, that the server compiled under Cygwin is
unstable.
.PP
Install MySQL (if you havn't already)
.IP "\-" 4
download the MySQL Windows Binaries from
http://www.mysql.com/downloads/index.html
.IP "\-" 4
unzip mysql\-<version>\-win.zip into some temporary location
.IP "\-" 4
start the setup.exe there and follow the instructions
.IP "\-" 4
start the server
.IP "\-" 4
alternatively download, install and start the server on a remote
server, on what supported \s-1OS\s0 ever
.PP
Build MySQL clients under Cygwin:
.IP "\-" 4
download the MySQL \s-1LINUX\s0 source from
http://www.mysql.com/downloads/index.html
.IP "\-" 4
unpack mysql\-<version>.tar.gz into some tmp location
.IP "\-" 4
cd into the unpacked dir mysql\-<version>
.Sp
.Vb 1
\&  ./configure \-\-prefix=/usr/local/mysql \-\-without\-server
.Ve
.Sp
This prepares the Makefile with the installed Cygwin features. It
takes some time, but should finish without error. The 'prefix', as
given, installs the whole Cygwin/MySQL thingy into a location not
normally in your \s-1PATH\s0, so that you continue to use already installed
Windows binaries. The \-\-without\-server parameter tells configure to
only build the clients.
.IP "\-" 4
.Vb 1
\&  make
.Ve
.Sp
This builds all MySQL client parts ... be patient. It should finish
finally without any error.
.IP "\-" 4
.Vb 1
\&  make install
.Ve
.Sp
This installs the compiled client files under /usr/local/mysql/.
Remember, you don't need anything except the library under
/usr/local/mysql/lib and the headers under /usr/local/mysql/include!
.Sp
Essentially you are now done with this part. If you want, you may try
your compiled binaries shortly; for that, do:
.IP "\-" 4
.Vb 2
\&  cd /usr/local/mysql/bin
\&  ./mysql \-h 127.0.0.1
.Ve
.Sp
The host (\-h) parameter 127.0.0.1 targets the local host, but forces
the mysql client to use a \s-1TCP/IP\s0 connection. The default would be a
pipe/socket connection (even if you say '\-h localhost') and this
doesn't work between Cygwin and Windows (as far as I know).
.Sp
If you have your MySQL server running on some other box, then please
substitute '127.0.0.1' with the name or IP-number of that box.
.PP
Please note, in my environment the 'mysql' client did not accept a
simple \s-1RETURN\s0, I had to use CTRL-RETURN to send commands
\&... strange,
but I didn't attempt to fix that, as we are only interested in the
built lib and headers.
.PP
At the 'mysql>' prompt do a quick check:
.PP
.Vb 4
\&  mysql> use mysql
\&  mysql> show tables;
\&  mysql> select * from db;
\&  mysql> exit
.Ve
.PP
You are now ready to build DBD::mysql!
.PP
Build DBD::mysql:
.IP "\-" 4
download DBD\-mysql\-<version>.tar.gz from \s-1CPAN\s0
.IP "\-" 4
unpack DBD\-mysql\-<version>.tar.gz
.IP "\-" 4
cd into unpacked dir DBD\-mysql\-<version>
you probably did that already, if you are reading this!
.IP "\-" 4
.Vb 1
\&  cp /usr/local/mysql/bin/mysql_config .
.Ve
.Sp
This copies the executable script mentioned in the DBD::mysql docs
from your just built Cywin/MySQL client directory; it knows about
your Cygwin installation, especially about the right libraries to link
with.
.IP "\-" 4
.Vb 1
\&  perl Makefile.PL \-\-testhost=127.0.0.1
.Ve
.Sp
The \-\-testhost=127.0.0.1 parameter again forces a \s-1TCP/IP\s0 connection
to the MySQL server on the local host instead of a pipe/socket
connection for the 'make test' phase.
.IP "\-" 4
.Vb 1
\&  make
.Ve
.Sp
This should run without error
.IP "\-" 4
.Vb 1
\&  make test
.Ve
.Sp
with DBD\-mysql\-2.1022 or earlier you will see several errors in
dbdadmin.t, mysql.t and mysql2.t; with later versions you should not
get errors (except possibly one, indicating, that some tables could
not be dropped. I'm hunting for a solution to that problem, but have
none yet).
.IP "\-" 4
.Vb 1
\&  make install
.Ve
.Sp
This installs DBD::mysql into the Perl hierarchy.
.PP
Notes:
.PP
This was tested with MySQL version 3.23.54a and DBD::mysql version
2.1022. I patched the above mentioned test scripts and sent the
patches
to the author of DBD::mysql Jochen Wiedman.
.PP
Georg Rehfeld          15. Jan. 2003
.SH "KNOWN PROBLEMS"
.IX Header "KNOWN PROBLEMS"
.IP "1.)" 4
.IX Item "1.)"
Some Linux distributions don't come with a gzip library by default.
Running \*(L"make\*(R" terminates with an error message like
.Sp
.Vb 8
\&  LD_RUN_PATH="/usr/lib/mysql:/lib:/usr/lib" gcc
\&    \-o blib/arch/auto/DBD/mysql/mysql.so  \-shared
\&    \-L/usr/local/lib dbdimp.o mysql.o \-L/usr/lib/mysql
\&    \-lmysqlclient \-lm \-L/usr/lib/gcc\-lib/i386\-redhat\-linux/2.96
\&    \-lgcc \-lz 
\&  /usr/bin/ld: cannot find \-lz
\&  collect2: ld returned 1 exit status
\&  make: *** [blib/arch/auto/DBD/mysql/mysql.so] Error 1
.Ve
.Sp
If this is the case for you, install an \s-1RPM\s0 archive like
libz-devel, libgz-devel, zlib-devel or gzlib-devel or something
similar.
.IP "2.)" 4
.IX Item "2.)"
If Perl was compiled with gcc or egcs, but MySQL was compiled
with another compiler or on another system, an error message like
this is very likely when running \*(L"Make test\*(R":
.Sp
.Vb 5
\&  t/00base............install_driver(mysql) failed: Can\*(Aqt load
\&  \*(Aq../blib/arch/auto/DBD/mysql/mysql.so\*(Aq for module DBD::mysql:
\&  ../blib/arch/auto/DBD/mysql/mysql.so: undefined symbol: _umoddi3
\&  at /usr/local/perl\-5.005/lib/5.005/i586\-linux\-thread/DynaLoader.pm
\&  line 168.
.Ve
.Sp
This means, that your linker doesn't include libgcc.a. You have
the following options:
.Sp
The solution is telling the linker to use libgcc. Run
.Sp
.Vb 1
\&  gcc \-\-print\-libgcc\-file
.Ve
.Sp
to determine the exact location of libgcc.a or for older versions
of gcc
.Sp
.Vb 1
\&  gcc \-v
.Ve
.Sp
to determine the directory. If you know the directory, add a
.Sp
.Vb 1
\&  \-L<directory> \-lgcc
.Ve
.Sp
to the list of C compiler flags. \*(L"Configuration\*(R". \*(L"Linker flags\*(R".
.IP "3.)" 4
.IX Item "3.)"
There are known problems with shared versions of libmysqlclient,
at least on some Linux boxes. If you receive an error message
similar to
.Sp
.Vb 4
\&  install_driver(mysql) failed: Can\*(Aqt load
\&  \*(Aq/usr/lib/perl5/site_perl/i586\-linux/auto/DBD/mysql/mysql.so\*(Aq
\&  for module DBD::mysql: File not found at
\&  /usr/lib/perl5/i586\-linux/5.00404/DynaLoader.pm line 166
.Ve
.Sp
then this error message can be misleading: It's not mysql.so
that fails being loaded, but libmysqlclient.so! The usual
problem is that this file is located in a directory like
.Sp
.Vb 1
\&  /usr/lib/mysql
.Ve
.Sp
where the linker doesn't look for it.
.Sp
The best workaround is using a statically linked mysqlclient
library, for example
.Sp
.Vb 1
\&  /usr/lib/mysql/libmysqlclient.a
.Ve
.Sp
The use of a statically linked library is described in the
previous section on linker flags. \*(L"Configuration\*(R".
\&\*(L"Linker flags\*(R".
.IP "4.)" 4
.IX Item "4.)"
Red Hat 8 & 9 set the Default locale to \s-1UTF\s0 which causes problems with 
MakeMaker.  To build DBD::mysql on these systems, do a 'unset \s-1LANG\s0' 
before runing 'perl Makefile.PL'
.SH "SUPPORT"
.IX Header "SUPPORT"
Finally, if everything else fails, you are not alone. First of
all, for an immediate answer, you should look into the archives
of the mailing list \[e-mail]\fR. See
http://www.mysql.com for archive locations.
.PP
If you don't find an appropriate posting and reply in the
mailing list, please post a question. Typically a reply will
be seen within one or two days.