perlmacosx.1

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

\&                           \-B$SDK/usr/lib/gcc \-isystem$SDK/usr/include \e
\&                           \-F$SDK/System/Library/Frameworks" \e
\&                \-Aldflags="\-arch i686 \-arch ppc \-Wl,\-syslibroot,$SDK" \e
\&                \-de
.Ve
.PP
Keep in mind that these compiler and linker settings will also be used when
building \s-1CPAN\s0 modules. For \s-1XS\s0 modules to be compiled as a universal binary, any
libraries it links to must also be universal binaries. The system libraries that
Apple includes with the 10.4u \s-1SDK\s0 are all universal, but user-installed libraries
may need to be re-installed as universal binaries.
.Sh "64\-bit \s-1PPC\s0 support"
.IX Subsection "64-bit PPC support"
Follow the instructions in \fI\s-1INSTALL\s0\fR to build perl with support for 64\-bit 
integers (\f(CW\*(C`use64bitint\*(C'\fR) or both 64\-bit integers and 64\-bit addressing
(\f(CW\*(C`use64bitall\*(C'\fR). In the latter case, the resulting binary will run only
on G5\-based hosts.
.PP
Support for 64\-bit addressing is experimental: some aspects of Perl may be
omitted or buggy. Note the messages output by \fIConfigure\fR for further 
information. Please use \f(CW\*(C`perlbug\*(C'\fR to submit a problem report in the
event that you encounter difficulties.
.PP
When building 64\-bit modules, it is your responsiblity to ensure that linked
external libraries and frameworks provide 64\-bit support: if they do not,
module building may appear to succeed, but attempts to use the module will
result in run-time dynamic linking errors, and subsequent test failures.
You can use \f(CW\*(C`file\*(C'\fR to discover the architectures supported by a library:
.PP
.Vb 4
\&    $ file libgdbm.3.0.0.dylib 
\&    libgdbm.3.0.0.dylib: Mach\-O fat file with 2 architectures
\&    libgdbm.3.0.0.dylib (for architecture ppc):      Mach\-O dynamically linked shared library ppc
\&    libgdbm.3.0.0.dylib (for architecture ppc64):    Mach\-O 64\-bit dynamically linked shared library ppc64
.Ve
.PP
Note that this issue precludes the building of many Macintosh-specific \s-1CPAN\s0
modules (\f(CW\*(C`Mac::*\*(C'\fR), as the required Apple frameworks do not provide \s-1PPC64\s0
support. Similarly, downloads from Fink or Darwinports are unlikely to provide
64\-bit support; the libraries must be rebuilt from source with the appropriate
compiler and linker flags. For further information, see Apple's
\&\fI64\-Bit Transition Guide\fR at 
<http://developer.apple.com/documentation/Darwin/Conceptual/64bitPorting/index.html>.
.Sh "libperl and Prebinding"
.IX Subsection "libperl and Prebinding"
Mac \s-1OS\s0 X ships with a dynamically-loaded libperl, but the default for
this release is to compile a static libperl. The reason for this is
pre-binding. Dynamic libraries can be pre-bound to a specific address in
memory in order to decrease load time. To do this, one needs to be aware
of the location and size of all previously-loaded libraries. Apple
collects this information as part of their overall \s-1OS\s0 build process, and
thus has easy access to it when building Perl, but ordinary users would
need to go to a great deal of effort to obtain the information needed
for pre-binding.
.PP
You can override the default and build a shared libperl if you wish
(Configure\ ...\ \-Duseshrlib), but the load time on pre\-10.4 \s-1OS\s0
releases will be greater than either the static library, or Apple's
pre-bound dynamic library.
.PP
With 10.4 \*(L"Tiger\*(R" and newer, Apple has all but eliminated the performance
penalty for non-prebound libraries.
.Sh "Updating Apple's Perl"
.IX Subsection "Updating Apple's Perl"
In a word \- don't, at least without a *very* good reason. Your scripts
can just as easily begin with \*(L"#!/usr/local/bin/perl\*(R" as with
\&\*(L"#!/usr/bin/perl\*(R". Scripts supplied by Apple and other third parties as
part of installation packages and such have generally only been tested
with the /usr/bin/perl that's installed by Apple.
.PP
If you find that you do need to update the system Perl, one issue worth
keeping in mind is the question of static vs. dynamic libraries. If you
upgrade using the default static libperl, you will find that the dynamic
libperl supplied by Apple will not be deleted. If both libraries are
present when an application that links against libperl is built, ld will
link against the dynamic library by default. So, if you need to replace
Apple's dynamic libperl with a static libperl, you need to be sure to
delete the older dynamic library after you've installed the update.
.Sh "Known problems"
.IX Subsection "Known problems"
If you have installed extra libraries such as \s-1GDBM\s0 through Fink
(in other words, you have libraries under \fI/sw/lib\fR), or libdlcompat
to \fI/usr/local/lib\fR, you may need to be extra careful when running
Configure to not to confuse Configure and Perl about which libraries
to use.  Being confused will show up for example as \*(L"dyld\*(R" errors about
symbol problems, for example during \*(L"make test\*(R". The safest bet is to run
Configure as
.PP
.Vb 1
\&    Configure ... \-Uloclibpth \-Dlibpth=/usr/lib
.Ve
.PP
to make Configure look only into the system libraries.  If you have some
extra library directories that you really want to use (such as newer
Berkeley \s-1DB\s0 libraries in pre-Panther systems), add those to the libpth:
.PP
.Vb 1
\&    Configure ... \-Uloclibpth \-Dlibpth=\*(Aq/usr/lib /opt/lib\*(Aq
.Ve
.PP
The default of building Perl statically may cause problems with complex
applications like Tk: in that case consider building shared Perl
.PP
.Vb 1
\&    Configure ... \-Duseshrplib
.Ve
.PP
but remember that there's a startup cost to pay in that case (see above
\&\*(L"libperl and Prebinding\*(R").
.PP
Starting with Tiger (Mac \s-1OS\s0 X 10.4), Apple shipped broken locale files for
the eu_ES locale (Basque-Spain).  In previous releases of Perl, this resulted in
failures in the \f(CW\*(C`lib/locale\*(C'\fR test. These failures have been supressed
in the current release of Perl by making the test ignore the broken locale.
If you need to use the eu_ES locale, you should contact Apple support.
.Sh "MacPerl"
.IX Subsection "MacPerl"
Quite a bit has been written about MacPerl, the Perl distribution for
\&\*(L"Classic MacOS\*(R" \- that is, versions 9 and earlier of MacOS. Because it
runs in environment that's very different from that of \s-1UNIX\s0, many things
are done differently in MacPerl. Modules are installed using a different
procedure, Perl itself is built differently, path names are different,
etc.
.PP
From the perspective of a Perl programmer, Mac \s-1OS\s0 X is more like a
traditional \s-1UNIX\s0 than Classic MacOS. If you find documentation that
refers to a special procedure that's needed for MacOS that's drastically
different from the instructions provided for \s-1UNIX\s0, the MacOS
instructions are quite often intended for MacPerl on Classic MacOS. In
that case, the correct procedure on Mac \s-1OS\s0 X is usually to follow the
\&\s-1UNIX\s0 instructions, rather than the MacPerl instructions.
.Sh "Carbon"
.IX Subsection "Carbon"
MacPerl ships with a number of modules that are used to access the
classic MacOS toolbox. Many of these modules have been updated to use
Mac \s-1OS\s0 X's newer \*(L"Carbon\*(R" toolbox, and are available from \s-1CPAN\s0 in the
\&\*(L"Mac::Carbon\*(R" module.
.Sh "Cocoa"
.IX Subsection "Cocoa"
There are two ways to use Cocoa from Perl. Apple's PerlObjCBridge
module, included with Mac \s-1OS\s0 X, can be used by standalone scripts to
access Foundation (i.e. non-GUI) classes and objects.
.PP
An alternative is CamelBones, a framework that allows access to both
Foundation and AppKit classes and objects, so that full \s-1GUI\s0 applications
can be built in Perl. CamelBones can be found on SourceForge, at
<http://www.sourceforge.net/projects/camelbones/>.
.SH "Starting From Scratch"
.IX Header "Starting From Scratch"
Unfortunately it is not that difficult somehow manage to break one's
Mac \s-1OS\s0 X Perl rather severely.  If all else fails and you want to
really, \fB\s-1REALLY\s0\fR, start from scratch and remove even your Apple Perl
installation (which has become corrupted somehow), the following
instructions should do it.  \fBPlease think twice before following
these instructions: they are much like conducting brain surgery to
yourself.  Without anesthesia.\fR  We will \fBnot\fR come to fix your system
if you do this.
.PP
First, get rid of the libperl.dylib:
.PP
.Vb 2
\&    # cd /System/Library/Perl/darwin/CORE
\&    # rm libperl.dylib
.Ve
.PP
Then delete every .bundle file found anywhere in the folders:
.PP
.Vb 2
\&    /System/Library/Perl
\&    /Library/Perl
.Ve
.PP
You can find them for example by
.PP
.Vb 1
\&    # find /System/Library/Perl /Library/Perl \-name \*(Aq*.bundle\*(Aq \-print
.Ve
.PP
After this you can either copy Perl from your operating system media
(you will need at least the /System/Library/Perl and /usr/bin/perl),
or rebuild Perl from the source code with \f(CW\*(C`Configure \-Dprefix=/usr
\&\-Dusershrplib\*(C'\fR \s-1NOTE:\s0 the \f(CW\*(C`\-Dprefix=/usr\*(C'\fR to replace the system Perl
works much better with Perl 5.8.1 and later, in Perl 5.8.0 the
settings were not quite right.
.PP
\&\*(L"Pacifist\*(R" from CharlesSoft (<http://www.charlessoft.com/>) is a nice
way to extract the Perl binaries from the \s-1OS\s0 media, without having to
reinstall the entire \s-1OS\s0.
.SH "AUTHOR"
.IX Header "AUTHOR"
This \s-1README\s0 was written by Sherm Pendley <sherm@dot\-app.org>,
and subsequently updated by Dominic Dunlop <[e-mail]>.
The \*(L"Starting From Scratch\*(R" recipe was contributed by John Montbriand
<[e-mail]>.
.SH "DATE"
.IX Header "DATE"
Last modified 2006\-02\-24.