os/persistentdata/persistentstorage/sqlite3api/TEST/TCL/tcldistribution/unix/README
1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/os/persistentdata/persistentstorage/sqlite3api/TEST/TCL/tcldistribution/unix/README Fri Jun 15 03:10:57 2012 +0200
1.3 @@ -0,0 +1,149 @@
1.4 +Tcl UNIX README
1.5 +---------------
1.6 +
1.7 +RCS: @(#) $Id: README,v 1.24.2.2 2005/12/03 00:35:44 das Exp $
1.8 +
1.9 +This is the directory where you configure, compile, test, and install
1.10 +UNIX versions of Tcl. This directory also contains source files for Tcl
1.11 +that are specific to UNIX. Some of the files in this directory are
1.12 +used on the PC or Mac platform too, but they all depend on UNIX
1.13 +(POSIX/ANSI C) interfaces and some of them only make sense under UNIX.
1.14 +
1.15 +Updated forms of the information found in this file is available at:
1.16 + http://www.tcl.tk/doc/howto/compile.html#unix
1.17 +
1.18 +For information on platforms where Tcl is known to compile, along
1.19 +with any porting notes for getting it to work on those platforms, see:
1.20 + http://www.tcl.tk/software/tcltk/platforms.html
1.21 +
1.22 +The rest of this file contains instructions on how to do this. The
1.23 +release should compile and run either "out of the box" or with trivial
1.24 +changes on any UNIX-like system that approximates POSIX, BSD, or System
1.25 +V. We know that it runs on workstations from Sun, H-P, DEC, IBM, and
1.26 +SGI, as well as PCs running Linux, BSDI, and SCO UNIX. To compile for
1.27 +a PC running Windows, see the README file in the directory ../win. To
1.28 +compile for Max OS X, see the README in the directory ../macosx. To
1.29 +compile for a classic Macintosh, see the README file in the directory ../mac.
1.30 +
1.31 +How To Compile And Install Tcl:
1.32 +-------------------------------
1.33 +
1.34 +(a) If you have already compiled Tcl once in this directory and are now
1.35 + preparing to compile again in the same directory but for a different
1.36 + platform, or if you have applied patches, type "make distclean" to
1.37 + discard all the configuration information computed previously.
1.38 +
1.39 +(b) If you need to reconfigure because you changed any of the .in or
1.40 + .m4 files, you will need to run autoconf to create a new
1.41 + ./configure script. Most users will NOT need to do this since
1.42 + a configure script is already provided.
1.43 +
1.44 + (in the tcl/unix directory)
1.45 + autoconf
1.46 +
1.47 +(c) Type "./configure". This runs a configuration script created by GNU
1.48 + autoconf, which configures Tcl for your system and creates a
1.49 + Makefile. The configure script allows you to customize the Tcl
1.50 + configuration for your site; for details on how you can do this,
1.51 + type "./configure -help" or refer to the autoconf documentation (not
1.52 + included here). Tcl's "configure" supports the following special
1.53 + switches in addition to the standard ones:
1.54 + --enable-threads If this switch is set, Tcl will compile
1.55 + itself with multithreading support.
1.56 + --disable-load If this switch is specified then Tcl will
1.57 + configure itself not to allow dynamic loading,
1.58 + even if your system appears to support it.
1.59 + Normally you can leave this switch out and
1.60 + Tcl will build itself for dynamic loading
1.61 + if your system supports it.
1.62 + --enable-shared If this switch is specified, Tcl will compile
1.63 + itself as a shared library if it can figure
1.64 + out how to do that on this platform. This
1.65 + is the default on platforms where we know
1.66 + how to build shared libraries.
1.67 + --disable-shared If this switch is specified, Tcl will compile
1.68 + itself as a static library.
1.69 + --enable-symbols build with debugging symbols. By default
1.70 + standard debugging symbols are used. You
1.71 + can specify the value "mem" to include
1.72 + TCL_MEM_DEBUG memory debugging, "compile"
1.73 + to include TCL_COMPILE_DEBUG debugging, or
1.74 + "all" to enable all internal debugging.
1.75 + --disable-symbols build without debugging symbols
1.76 + --enable-64bit enable 64bit support (where applicable)
1.77 + --disable-64bit disable 64bit support (where applicable)
1.78 + --enable-64bit-vis enable 64bit Sparc VIS support
1.79 + --disable-64bit-vis disable 64bit Sparc VIS support
1.80 + --enable-langinfo Allows use of modern nl_langinfo check for
1.81 + better localization support. This is on by
1.82 + default on platforms where nl_langinfo is
1.83 + found.
1.84 + --disable-langinfo Specifically disables use of nl_langinfo.
1.85 + --enable-man-symlinks Use symlinks for linking the manpages that
1.86 + should be reachable under several names.
1.87 + --enable-man-compression=PROG
1.88 + Compress the manpages using PROG.
1.89 + Mac OS X only:
1.90 + --enable-framework package Tcl as a framework.
1.91 + --disable-corefoundation disable use of CoreFoundation API and revert to
1.92 + standard select based notifier, required when
1.93 + using naked fork (i.e. not followed by execve).
1.94 +
1.95 + Note: by default gcc will be used if it can be located on the PATH.
1.96 + if you want to use cc instead of gcc, set the CC environment variable
1.97 + to "cc" before running configure. It is not safe to edit the
1.98 + Makefile to use gcc after configure is run. Also note that
1.99 + you should use the same compiler when building extensions.
1.100 +
1.101 + Note: be sure to use only absolute path names (those starting with "/")
1.102 + in the --prefix and --exec-prefix options.
1.103 +
1.104 +(d) Type "make". This will create a library archive called
1.105 + "libtcl<version>.a" or "libtcl<version>.so" and an interpreter
1.106 + application called "tclsh" that allows you to type Tcl commands
1.107 + interactively or execute script files.
1.108 +
1.109 +(e) If the make fails then you'll have to personalize the Makefile
1.110 + for your site or possibly modify the distribution in other ways.
1.111 + First check the porting Web page above to see if there are hints
1.112 + for compiling on your system. If you need to modify Makefile,
1.113 + are comments at the beginning of it that describe the things you
1.114 + might want to change and how to change them.
1.115 +
1.116 +(f) Type "make install" to install Tcl binaries and script files in
1.117 + standard places. You'll need write permission on the installation
1.118 + directories to do this. The installation directories are
1.119 + determined by the "configure" script and may be specified with
1.120 + the --prefix and --exec-prefix options to "configure". See the
1.121 + Makefile for information on what directories were chosen; you
1.122 + can override these choices by modifying the "prefix" and
1.123 + "exec_prefix" variables in the Makefile.
1.124 +
1.125 +(g) At this point you can play with Tcl by running "make shell"
1.126 + and typing Tcl commands at the prompt.
1.127 +
1.128 +If you have trouble compiling Tcl, see the URL noted above about working
1.129 +platforms. It contains information that people have provided about changes
1.130 +they had to make to compile Tcl in various environments. We're also
1.131 +interested in hearing how to change the configuration setup so that Tcl
1.132 +compiles on additional platforms "out of the box".
1.133 +
1.134 +Test suite
1.135 +----------
1.136 +
1.137 +There is a relatively complete test suite for all of the Tcl core in
1.138 +the subdirectory "tests". To use it just type "make test" in this
1.139 +directory. You should then see a printout of the test files processed.
1.140 +If any errors occur, you'll see a much more substantial printout for
1.141 +each error. See the README file in the "tests" directory for more
1.142 +information on the test suite. Note: don't run the tests as superuser:
1.143 +this will cause several of them to fail. If a test is failing
1.144 +consistently, please send us a bug report with as much detail as you
1.145 +can manage. Please use the online database at
1.146 + http://tcl.sourceforge.net/
1.147 +
1.148 +The Tcl test suite is very sensitive to proper implementation of
1.149 +ANSI C library procedures such as sprintf and sscanf. If the test
1.150 +suite generates errors, most likely they are due to non-conformance
1.151 +of your system's ANSI C library; such problems are unlikely to
1.152 +affect any real applications so it's probably safe to ignore them.