Gecko [ www.utparral.edu.mx ]

Name	Size	Permission
about.htm	5.13 KB	-rw-r--r--
aboutunicode.htm	6.69 KB	-rw-r--r--
acknowledgments.htm	4.39 KB	-rw-r--r--
advocacy.htm	3.67 KB	-rw-r--r--
ambition.htm	3.52 KB	-rw-r--r--
apireference.htm	4.71 KB	-rw-r--r--
appendmode.htm	4.1 KB	-rw-r--r--
askingforhelp.htm	5.36 KB	-rw-r--r--
build.htm	4.73 KB	-rw-r--r--
choosingtdsprotocol.htm	6.62 KB	-rw-r--r--
config.htm	17.16 KB	-rw-r--r--
configs.htm	4.9 KB	-rw-r--r--
confirminstall.htm	16.33 KB	-rw-r--r--
contrib.htm	5.98 KB	-rw-r--r--
contributors.htm	2.47 KB	-rw-r--r--
ctlib.api.summary.htm	14.88 KB	-rw-r--r--
dblib.api.summary.htm	28.32 KB	-rw-r--r--
domains.htm	6.22 KB	-rw-r--r--
dsnless.htm	5.96 KB	-rw-r--r--
envvar.htm	6.93 KB	-rw-r--r--
freetdsconf.htm	18.39 KB	-rw-r--r--
freetdshistory.htm	4.45 KB	-rw-r--r--
gfdl-10.htm	3.11 KB	-rw-r--r--
gfdl-11.htm	3.32 KB	-rw-r--r--
gfdl-1.htm	5.42 KB	-rw-r--r--
gfdl-2.htm	2.9 KB	-rw-r--r--
gfdl-3.htm	4.18 KB	-rw-r--r--
gfdl-4.htm	7.25 KB	-rw-r--r--
gfdl-5.htm	3.37 KB	-rw-r--r--
gfdl-6.htm	2.83 KB	-rw-r--r--
gfdl-7.htm	3.07 KB	-rw-r--r--
gfdl-8.htm	2.8 KB	-rw-r--r--
gfdl-9.htm	2.6 KB	-rw-r--r--
gfdl.htm	4.46 KB	-rw-r--r--
help.htm	5.31 KB	-rw-r--r--
index.htm	23.65 KB	-rw-r--r--
index.html	23.65 KB	-rw-r--r--
install.htm	5.59 KB	-rw-r--r--
interfacesfile.htm	3.64 KB	-rw-r--r--
interfacesformat.htm	4.71 KB	-rw-r--r--
interfaceslocation.htm	2.45 KB	-rw-r--r--
interfacespurpose.htm	4.83 KB	-rw-r--r--
iso8859.htm	5.31 KB	-rw-r--r--
isolatecause.htm	4.39 KB	-rw-r--r--
kerberos.htm	3.92 KB	-rw-r--r--
light.taper.htm	3.03 KB	-rw-r--r--
linker.conclusion.htm	2.75 KB	-rw-r--r--
linker.how.htm	13.61 KB	-rw-r--r--
linker.library.check.htm	5.31 KB	-rw-r--r--
locales.htm	6.89 KB	-rw-r--r--
localization.htm	11.32 KB	-rw-r--r--
logging.htm	7.35 KB	-rw-r--r--
mailinglist.htm	4.1 KB	-rw-r--r--
name.lookup.htm	4.14 KB	-rw-r--r--
odbc.api.summary.htm	16.65 KB	-rw-r--r--
odbcconnattr.htm	7.31 KB	-rw-r--r--
odbcdiagnose.htm	8.88 KB	-rw-r--r--
odbcinionly.htm	3.47 KB	-rw-r--r--
odbcombo.htm	4.44 KB	-rw-r--r--
osissues.htm	10.13 KB	-rw-r--r--
packages.htm	4.43 KB	-rw-r--r--
pagenodata.htm	5.88 KB	-rw-r--r--
perl.htm	7.36 KB	-rw-r--r--
php.htm	7.73 KB	-rw-r--r--
portoverride.htm	3.86 KB	-rw-r--r--
prepodbc.htm	9.89 KB	-rw-r--r--
programming.htm	2.76 KB	-rw-r--r--
projects.htm	11.26 KB	-rw-r--r--
python.htm	4.01 KB	-rw-r--r--
qt.htm	2.69 KB	-rw-r--r--
rtl.define.library.htm	8.43 KB	-rw-r--r--
rtl.htm	7.22 KB	-rw-r--r--
samplecode.htm	48.19 KB	-rw-r--r--
seemtooslow.htm	4.72 KB	-rw-r--r--
serverthere.htm	6.59 KB	-rw-r--r--
software.htm	5.79 KB	-rw-r--r--
stunnel.htm	4.11 KB	-rw-r--r--
sybsql.htm	4.56 KB	-rw-r--r--
tdshistory.htm	5.16 KB	-rw-r--r--
tdspool.htm	7.72 KB	-rw-r--r--
troubleshooting.htm	10.84 KB	-rw-r--r--
unicodefreetds.htm	4.96 KB	-rw-r--r--
unicodegoodbad.htm	4.99 KB	-rw-r--r--
unicode.htm	4.07 KB	-rw-r--r--
unicodeutf.htm	5.32 KB	-rw-r--r--
uodbc.htm	5.7 KB	-rw-r--r--
uothread.htm	3.19 KB	-rw-r--r--
usefreetds.htm	6.26 KB	-rw-r--r--
userguide.css	295 B	-rw-r--r--
what.htm	7.85 KB	-rw-r--r--

Code Editor : config.htm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<HTML
><HEAD
><TITLE
>How to build: Configure and make</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="FreeTDS User Guide"
HREF="index.htm"><LINK
REL="UP"
TITLE="Build FreeTDS"
HREF="build.htm"><LINK
REL="PREVIOUS"
TITLE="What to build: Packages, Tarballs, and the CVS repository"
HREF="packages.htm"><LINK
REL="NEXT"
TITLE="OS-specific Issues"
HREF="osissues.htm"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="userguide.css"><META
HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=utf-8"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>FreeTDS User Guide: A Guide to Installing, Configuring, and Running FreeTDS</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="packages.htm"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 2. Build FreeTDS</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="osissues.htm"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="CONFIG"
>How to build: Configure and make</A
></H1
>If you've built other <ACRONYM
CLASS="ACRONYM"
>GNU</ACRONYM
> projects, building FreeTDS is a fairly straightforward process. We have a terse and verbose description.<DIV
CLASS="NOTE"
><TABLE
CLASS="NOTE"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>FreeTDS is known to build with <ACRONYM
CLASS="ACRONYM"
>GNU</ACRONYM
> and <ACRONYM
CLASS="ACRONYM"
>BSD</ACRONYM
> make. If you encounter a large number of build errors, and your operating system's make is not <ACRONYM
CLASS="ACRONYM"
>GNU</ACRONYM
> make (as is the case on most non-<ACRONYM
CLASS="ACRONYM"
>GNU</ACRONYM
>/Linux systems), you may wish to install <ACRONYM
CLASS="ACRONYM"
>GNU</ACRONYM
> make from <A
HREF="ftp://ftp.gnu.org/gnu/make/"
TARGET="_top"
>ftp.gnu.org</A
>.</TD
></TR
></TABLE
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="EXPERTS"
>For Experts</A
></H2
><PRE
CLASS="SCREEN"
>	<SAMP
CLASS="PROMPT"
>$ </SAMP
><KBD
CLASS="USERINPUT"
>./configure --prefix=/usr/local</KBD
>
	<SAMP
CLASS="PROMPT"
>$ </SAMP
><KBD
CLASS="USERINPUT"
>make</KBD
>
	<SAMP
CLASS="PROMPT"
>$ </SAMP
><KBD
CLASS="USERINPUT"
>su root</KBD
>
	<SAMP
CLASS="PROMPT"
>Password: </SAMP
>
	<SAMP
CLASS="PROMPT"
>$ </SAMP
><KBD
CLASS="USERINPUT"
>make install</KBD
></PRE
>Building from CVS is described in the file <TT
CLASS="FILENAME"
>INSTALL.CVS</TT
>.</DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="EVERYONE"
>For Everyone Else</A
></H2
>The <ACRONYM
CLASS="ACRONYM"
>GNU</ACRONYM
> development system can generate code for a wide variety of hardware architectures and operating systems, virtually all of which can run FreeTDS in consequence. The work of building and installing the FreeTDS libraries begins with the command configure, which generates the <TT
CLASS="FILENAME"
>Makefile</TT
> that governs how the code is compiled, linked, and installed. Once you've "configured" the project, make will manage the rest of the build.<TABLE
CLASS="SIDEBAR"
BORDER="1"
CELLPADDING="5"
><TR
><TD
><DIV
CLASS="SIDEBAR"
><A
NAME="AEN435"
></A
>ODBC PreparationIf you intend to build the FreeTDS ODBC driver &mdash; and want to use a Driver Manager (DM), as most people do &mdash; install the Driver Manager before configuring FreeTDS. configure will detect the the DM and use its header (<TT
CLASS="FILENAME"
>.h</TT
>) files for ODBC constants and such. If your DM is installed in an unusual directory, you may have to provide the directory name as a parameter to configure.FreeTDS doesn't require a DM. You can build the ODBC driver without one, as long as you have the requisite header files: <TT
CLASS="FILENAME"
>sql.h</TT
>, <TT
CLASS="FILENAME"
>sqlext.h</TT
> and <TT
CLASS="FILENAME"
>sqltypes.h</TT
>. These can be taken from either the iODBC or UnixODBC distributions. Put them wherever you like (e.g., <TT
CLASS="FILENAME"
>/usr/local/include</TT
>). Because FreeTDS won't detect your (missing) DM, it won't automatically build the ODBC driver, so you'll have to tell configure what to do and where to look. Cf. <A
HREF="config.htm#WITHODBCNODM"
><CODE
CLASS="OPTION"
>--with-odbc-nodm</CODE
></A
>.</DIV
></TD
></TR
></TABLE
>The simplest form of running configure is:
<PRE
CLASS="SCREEN"
>	<SAMP
CLASS="PROMPT"
>$ </SAMP
><KBD
CLASS="USERINPUT"
>./configure</KBD
></PRE
>
	and sometimes that's enough. configure accepts command-line arguments, too, and you may need to provide some, depending on your environment.There are a few optional arguments to configure that may be important to you. For a complete list, see configure --help.<DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="CONFIGURE.OPTIONS"
>configure options</A
></H3
><DIV
CLASS="VARIABLELIST"
>Directories and TDS version<DL
><DT
><CODE
CLASS="OPTION"
>--prefix=<TT
CLASS="REPLACEABLE"
>PREFIX</TT
>
							</CODE
></DT
><DD
> install architecture-independent files in <CODE
CLASS="PARAMETER"
>PREFIX</CODE
>. When you run make install, libraries will be placed in <CODE
CLASS="PARAMETER"
>PREFIX</CODE
><TT
CLASS="FILENAME"
>/lib</TT
>, executables in <CODE
CLASS="PARAMETER"
>PREFIX</CODE
><TT
CLASS="FILENAME"
>/bin</TT
>, and so on.The default is <TT
CLASS="FILENAME"
>/usr/local</TT
> if this argument is not passed to configure.</DD
><DT
><CODE
CLASS="OPTION"
>--sysconfdir=<TT
CLASS="REPLACEABLE"
>DIR</TT
>
							</CODE
></DT
><DD
> read-only single-machine data in <CODE
CLASS="PARAMETER"
>DIR</CODE
>The default is <TT
CLASS="REPLACEABLE"
>PREFIX/etc</TT
> (<CODE
CLASS="PARAMETER"
>PREFIX</CODE
> being the value of <CODE
CLASS="OPTION"
>--prefix=<TT
CLASS="REPLACEABLE"
>PREFIX</TT
></CODE
>, above) if this argument is not passed to configure.</DD
><DT
><CODE
CLASS="OPTION"
>--with-libiconv-prefix=<TT
CLASS="REPLACEABLE"
>DIR</TT
>
							</CODE
></DT
><DD
>Specifies the location of the iconv library to use. configure will search for libiconv in the usual places; use <CODE
CLASS="OPTION"
>--with-libiconv-prefix</CODE
> if it's unsuccessful (assuming you want to use iconv, of course). Overridden by <CODE
CLASS="OPTION"
>--disable-libiconv</CODE
>, below.</DD
><DT
><CODE
CLASS="OPTION"
>--with-tdsver=<TT
CLASS="REPLACEABLE"
>VER</TT
>
							</CODE
></DT
><DD
>Specifies the default <ACRONYM
CLASS="ACRONYM"
>TDS</ACRONYM
> version. (There are a couple of ways to set the <ACRONYM
CLASS="ACRONYM"
>TDS</ACRONYM
> version at run-time. This parameter takes effect if no run-time settings are provided.) Acceptable values of <CODE
CLASS="PARAMETER"
>VER</CODE
> are <TT
CLASS="LITERAL"
>4.2</TT
>, <TT
CLASS="LITERAL"
>4.6</TT
>, <TT
CLASS="LITERAL"
>5.0</TT
>, <TT
CLASS="LITERAL"
>7.0</TT
>, <TT
CLASS="LITERAL"
>7.1</TT
> and <TT
CLASS="LITERAL"
>7.2</TT
>.The default is <TT
CLASS="LITERAL"
>5.0</TT
> if this argument is not passed to configure.</DD
></DL
></DIV
><DIV
CLASS="VARIABLELIST"
>ODBC Driver Managers<DL
><DT
><CODE
CLASS="OPTION"
>--with-iodbc=<TT
CLASS="REPLACEABLE"
>DIR</TT
>
							</CODE
>, <CODE
CLASS="OPTION"
>--with-unixodbc=<TT
CLASS="REPLACEABLE"
>DIR</TT
>
							</CODE
></DT
><DD
>Specify directory of iODBC or unixODBC support, and use it as the Driver Manager.
								As of version 0.62, the ODBC Driver Manager is detected by configure, so use this parameter only if yours is installed in a nonstandard path.
								(Requires iODBC or unixODBC to have already been installed.)</DD
><DT
><A
NAME="WITHODBCNODM"
></A
><CODE
CLASS="OPTION"
>--with-odbc-nodm=<TT
CLASS="REPLACEABLE"
>DIR</TT
>
								</CODE
></DT
><DD
>If you're building the ODBC driver and not using a Driver Manager, use this option to indicate the location of the <TT
CLASS="FILENAME"
>.h</TT
> files. configure will not cause the ODBC driver to be built unless this option is used or a DM is detected/specified.</DD
></DL
></DIV
><DIV
CLASS="VARIABLELIST"
>Things you can turn off<DL
><DT
><CODE
CLASS="OPTION"
>--disable-odbc
							</CODE
></DT
><DD
>Do not attempt to detect ODBC, and do not build the ODBC driver. In case you don't care about ODBC.</DD
><DT
><CODE
CLASS="OPTION"
>--disable-apps
							</CODE
></DT
><DD
>Do not attempt to build applications like tsql.</DD
><DT
><CODE
CLASS="OPTION"
>--disable-server
							</CODE
></DT
><DD
>Do not attempt to build server stuff.</DD
><DT
><CODE
CLASS="OPTION"
>--disable-pool
							</CODE
></DT
><DD
>Do not attempt to build pool stuff.</DD
><DT
><CODE
CLASS="OPTION"
>--disable-libiconv</CODE
></DT
><DD
>By default, configure will search your system for an iconv library for use with Microsoft servers (because TDS 7.0 employs Unicode). This switch prevents that search. If no iconv library is used, FreeTDS relies on its built-in iconv emulation, which is capable of converting ISO-8859-1 to UCS-2, sufficient for many applications.</DD
><DT
><CODE
CLASS="OPTION"
>--disable-threadsafe</CODE
></DT
><DD
>Force FreeTDS not to use threadsafe versions of functions such as <CODE
CLASS="FUNCTION"
>gethostbyname_r()</CODE
> where available. Rely instead on the older and non-threadsafe ones such as <CODE
CLASS="FUNCTION"
>gethostbyname()</CODE
>. configure tests some of these functions. If the tests are successful, FreeTDS will use threadsafe functions throughout.Threadsafe operation has been tested on Linux, FreeBSD, and HP-UX. It should work on Solaris, Tru64, and (reportedly) IRIX. Not expected to work on non-unixy systems. It is a good idea to enable threadsafe operation if you configure Apache with multi-threading support.</DD
><DT
><CODE
CLASS="OPTION"
>--disable-debug</CODE
></DT
><DD
>Debug-mode compiles are enabled by default, and will remain so at least until version 1.0. You can speed things up ever so slightly by disabling it.</DD
></DL
></DIV
><DIV
CLASS="VARIABLELIST"
>Things you can turn on<DL
><DT
><CODE
CLASS="OPTION"
>--enable-msdblib</CODE
></DT
><DD
>Enable Microsoft behavior in the DB-Library <ACRONYM
CLASS="ACRONYM"
>API</ACRONYM
> where it diverges from Sybase's. Use this option if you are replacing Microsoft's libraries with FreeTDSThis option specifies default behavior. Programs can change the default at compile time by defining MSDBLIB or SYBDBLIB (for Microsoft or Sybase behavior, respectively).</DD
><DT
><CODE
CLASS="OPTION"
>--enable-sybase-compat</CODE
></DT
><DD
>Enable close compatibility with Sybase's ABI, at the expense of other features. Currently, this enables the generation of a dbopen() entry point in DB-Library, which may clash with the DBM function with the same name. Absolutely not required for use with other free software.</DD
><DT
><CODE
CLASS="OPTION"
>--enable-krb5</CODE
></DT
><DD
>Enable Kerberos support. With Kerberos you can connect to server using your stored Kerberos ticket. Obviously requires Kerberos be configured on the machine.</DD
><DT
><CODE
CLASS="OPTION"
>--enable-sspi</CODE
></DT
><DD
>Enable SSPI support. SSPI is a Micrsoft library that allows you to use your current logged-in account for authentication. With this option enabled, FreeTDS supports "trusted logins" for Win32/64, just as Microsoft's own implementations do.</DD
><DT
><CODE
CLASS="OPTION"
>--enable-extra-checks</CODE
></DT
><DD
>Intended for debugging purposes, enables certain internal consistency checks against problems like memory corruption and buffer exhaustion.</DD
><DT
><CODE
CLASS="OPTION"
>--enable-developing</CODE
></DT
><DD
>Enable some code still in development. Should be used only by a developer or a brave user :)</DD
></DL
></DIV
><DIV
CLASS="VARIABLELIST"
>SSL support<DL
><DT
><CODE
CLASS="OPTION"
>--with-gnutls</CODE
></DT
><DD
>Enable SSL using GnuTLS. Use version 1.2.3 or newer.</DD
><DT
><CODE
CLASS="OPTION"
>--with-openssl=<TT
CLASS="REPLACEABLE"
>DIR</TT
></CODE
></DT
><DD
>Enable SSL using OpenSSL. Unlike FreeTDS, OpenSSL does not use the LGPL. Please read the <A
HREF="http://www.openssl.org/source/license.html"
TARGET="_top"
>OpenSSL license</A
> before distributing binaries compiled with this option.</DD
></DL
></DIV
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN648"
>Make</A
></H3
>Now you're ready to build. Follow these easy steps.<OL
TYPE="1"
><LI
>Download the tarball and unpack it.Alternatively, get the latest build from CVS
							<A
NAME="AEN657"
HREF="#FTN.AEN657"
>[1]</A
>
							.</LI
><LI
>Change to the <TT
CLASS="FILENAME"
>freetds</TT
> directory.</LI
><LI
>run ./configure with any options you need.</LI
><LI
>make; make install; make clean</LI
></OL
>You normally need to be root to make install, unless you used the <CODE
CLASS="OPTION"
>--prefix</CODE
> option during configuration to install into your own directory.With any luck, you've built and installed the FreeTDS libraries.<DIV
CLASS="TIP"
><TABLE
CLASS="TIP"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TH
ALIGN="LEFT"
VALIGN="MIDDLE"
>Two bits of advice, if you like to keep things tidy and keep track of what you did.</TH
></TR
><TR
><TD
>&nbsp;</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Create a file to hold your configure options called, say, <TT
CLASS="FILENAME"
>.build_options</TT
>.Create a build directory for the binaries, and invoke ../configure $(cat ../.build_options). This approach lets you remove the binaries at any time and rebuild from scratch using the same options.</TD
></TR
></TABLE
></DIV
></DIV
></DIV
></DIV
><H3
CLASS="FOOTNOTES"
>Notes</H3
><TABLE
BORDER="0"
CLASS="FOOTNOTES"
WIDTH="100%"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN657"
HREF="config.htm#AEN657"
>[1]</A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
>CVS users will need the GNU autotools: Autoconf, Automake, and libtool.</TD
></TR
></TABLE
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="packages.htm"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.htm"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="osissues.htm"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>What to build: Packages, Tarballs, and the CVS repository</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="build.htm"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>OS-specific Issues</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

${this.title}

Code Editor : config.htm