<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>[Freeswitch-trunk][15051] </title>
</head>
<body>
<style type="text/css"><!--
#msg dl.meta { border: 1px #006 solid; background: #369; padding: 6px; color: #fff; }
#msg dl.meta dt { float: left; width: 6em; font-weight: bold; }
#msg dt:after { content:':';}
#msg dl, #msg dt, #msg ul, #msg li, #header, #footer, #logmsg { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; }
#msg dl a { font-weight: bold}
#msg dl a:link { color:#fc3; }
#msg dl a:active { color:#ff0; }
#msg dl a:visited { color:#cc6; }
h3 { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; font-weight: bold; }
#msg pre { overflow: auto; background: #ffc; border: 1px #fa0 solid; padding: 6px; }
#logmsg { background: #ffc; border: 1px #fa0 solid; padding: 1em 1em 0 1em; }
#logmsg p, #logmsg pre, #logmsg blockquote { margin: 0 0 1em 0; }
#logmsg p, #logmsg li, #logmsg dt, #logmsg dd { line-height: 14pt; }
#logmsg h1, #logmsg h2, #logmsg h3, #logmsg h4, #logmsg h5, #logmsg h6 { margin: .5em 0; }
#logmsg h1:first-child, #logmsg h2:first-child, #logmsg h3:first-child, #logmsg h4:first-child, #logmsg h5:first-child, #logmsg h6:first-child { margin-top: 0; }
#logmsg ul, #logmsg ol { padding: 0; list-style-position: inside; margin: 0 0 0 1em; }
#logmsg ul { text-indent: -1em; padding-left: 1em; }#logmsg ol { text-indent: -1.5em; padding-left: 1.5em; }
#logmsg > ul, #logmsg > ol { margin: 0 0 1em 0; }
#logmsg pre { background: #eee; padding: 1em; }
#logmsg blockquote { border: 1px solid #fa0; border-left-width: 10px; padding: 1em 1em 0 1em; background: white;}
#logmsg dl { margin: 0; }
#logmsg dt { font-weight: bold; }
#logmsg dd { margin: 0; padding: 0 0 0.5em 0; }
#logmsg dd:before { content:'\00bb';}
#logmsg table { border-spacing: 0px; border-collapse: collapse; border-top: 4px solid #fa0; border-bottom: 1px solid #fa0; background: #fff; }
#logmsg table th { text-align: left; font-weight: normal; padding: 0.2em 0.5em; border-top: 1px dotted #fa0; }
#logmsg table td { text-align: right; border-top: 1px dotted #fa0; padding: 0.2em 0.5em; }
#logmsg table thead th { text-align: center; border-bottom: 1px solid #fa0; }
#logmsg table th.Corner { text-align: left; }
#logmsg hr { border: none 0; border-top: 2px dashed #fa0; height: 1px; }
#header, #footer { color: #fff; background: #636; border: 1px #300 solid; padding: 6px; }
#patch { width: 100%; }
#patch h4 {font-family: verdana,arial,helvetica,sans-serif;font-size:10pt;padding:8px;background:#369;color:#fff;margin:0;}
#patch .propset h4, #patch .binary h4 {margin:0;}
#patch pre {padding:0;line-height:1.2em;margin:0;}
#patch .diff {width:100%;background:#eee;padding: 0 0 10px 0;overflow:auto;}
#patch .propset .diff, #patch .binary .diff {padding:10px 0;}
#patch span {display:block;padding:0 10px;}
#patch .modfile, #patch .addfile, #patch .delfile, #patch .propset, #patch .binary, #patch .copfile {border:1px solid #ccc;margin:10px 0;}
#patch ins {background:#dfd;text-decoration:none;display:block;padding:0 10px;}
#patch del {background:#fdd;text-decoration:none;display:block;padding:0 10px;}
#patch .lines, .info {color:#888;background:#fff;}
--></style>
<div id="msg">
<div id="header">FreeSWITCH Subversion</div>
<dl class="meta">
<dt>Revision</dt> <dd><a href="http://fisheye.freeswitch.org/changelog/FreeSWITCH?cs=15051">15051</a></dd>
<dt>Author</dt> <dd>anthm</dd>
<dt>Date</dt> <dd>2009-10-02 10:07:18 -0500 (Fri, 02 Oct 2009)</dd>
</dl>
<h3>Log Message</h3>
<pre><a href="http://jira.freeswitch.org/browse/FSCORE-456">FSCORE-456</a></pre>
<h3>Modified Paths</h3>
<ul>
<li><a href="#freeswitchtrunklibsspandspINSTALL">freeswitch/trunk/libs/spandsp/INSTALL</a></li>
<li><a href="#freeswitchtrunksrcswitch_corec">freeswitch/trunk/src/switch_core.c</a></li>
</ul>
</div>
<div id="patch">
<h3>Diff</h3>
<a id="freeswitchtrunklibsspandspINSTALL"></a>
<div class="modfile"><h4>Modified: freeswitch/trunk/libs/spandsp/INSTALL (15050 => 15051)</h4>
<pre class="diff"><span>
<span class="info">--- freeswitch/trunk/libs/spandsp/INSTALL 2009-10-02 14:44:16 UTC (rev 15050)
+++ freeswitch/trunk/libs/spandsp/INSTALL 2009-10-02 15:07:18 UTC (rev 15051)
</span><span class="lines">@@ -1,100 +1,43 @@
</span><del>-Building and installing spandsp
-===============================
</del><ins>+Installation Instructions
+*************************
</ins><span class="cx">
</span><del>-A number of distributions include spandsp, but they usually use older versions
-of the library, which lack a lot of the features of the current version. Before
-installing spandsp, make sure there are no older versions already on your
-machine. Make sure libtiff is installed on your machine. Versions 3.5.7,
-3.6.0, 3.7.1 and 3.8.2 seem to work OK. There have been several bugs related
-to FAX document handling in some versions of libtiff. Also, some people have
-had trouble using spandsp because they had more than one version of libtiff
-on their machine. Take care with this. If you are using an RPM based system,
-such as RedHat or Fedora, you will need the libtiff and libtiff-devel RPMs
-installed to be able to build spandsp.
</del><ins>+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
+Software Foundation, Inc.
</ins><span class="cx">
</span><del>-You can use the usual:
</del><ins>+This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
</ins><span class="cx">
</span><del>- ./configure
- make
- make install
-
-process to build the spandsp library. Note that if you use configure in this
-way, the software will be installed in /usr/local. In this case make sure your
-/etc/ld.so.conf file has an entry for /usr/local/lib. If you wish the software
-to be installed in /usr, you should build it with the commands.
-
- ./configure --prefix=/usr
- make
- make install
-
-
-Building the programming documentation
-======================================
-
-If you wish to build the programming documentation for spandsp, configure
-spandsp with:
-
- ./configure --enable-doc
-
-You need doxygen installed on your machine.
-
-
-Building the test suite
-=======================
-
-Most sections of the spandsp library have an accompanying test program in the
-test directory. If you wish to build these test programs, configure spandsp
-with:
-
- ./configure --enable-tests
-
-To build these tests you will need libaudiofile installed on your machine. To
-build the modem tests, with the GUI monitoring feature you will need Fltk 1.1.4
-or later, an audio meter module and a cartesian plotting module. Fltk may be
-obtained from http://www.fltk.org. The audio meter module may be obtained from
-http://www.soft-switch.org/downloads/Fl_Audio_Meter.tgz . The cartesian plotting
-module may be obtained from http://134.226.68.29/fltk. However, there is no
-suitable makefile supplied with that. You can find a version at
-http://www.soft-switch.org/downloads/Fl_Cartesian.tgz which will build as a
-Linux library. The actual code in both these versions is identical.
-You need to have Fltk 1.1.4 or later installed before building the plotting
-library.
-
-
-Applications
-============
-
-Applications support for spandsp is built into packages such as Callweaver,
-FreeSwitch and iaxmodem. Code to add spandsp based FAX support to Asterisk may
-be found at http://sourceforge.net/projects/agx-ast-addons.
-
-
-
-
</del><span class="cx"> Basic Installation
</span><span class="cx"> ==================
</span><span class="cx">
</span><del>- These are generic installation instructions.
</del><ins>+These are generic installation instructions.
</ins><span class="cx">
</span><span class="cx"> The `configure' shell script attempts to guess correct values for
</span><span class="cx"> various system-dependent variables used during compilation. It uses
</span><span class="cx"> those values to create a `Makefile' in each directory of the package.
</span><span class="cx"> It may also create one or more `.h' files containing system-dependent
</span><span class="cx"> definitions. Finally, it creates a shell script `config.status' that
</span><del>-you can run in the future to recreate the current configuration, a file
-`config.cache' that saves the results of its tests to speed up
-reconfiguring, and a file `config.log' containing compiler output
-(useful mainly for debugging `configure').
</del><ins>+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
</ins><span class="cx">
</span><ins>+ It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring. (Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.)
+
</ins><span class="cx"> If you need to do unusual things to compile the package, please try
</span><span class="cx"> to figure out how `configure' could check whether to do them, and mail
</span><span class="cx"> diffs or instructions to the address given in the `README' so they can
</span><del>-be considered for the next release. If at some point `config.cache'
-contains results you don't want to keep, you may remove or edit it.
</del><ins>+be considered for the next release. If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
</ins><span class="cx">
</span><del>- The file `configure.ac' is used to create `configure' by a program
-called `autoconf'. You only need `configure.ac' if you want to change
-it or regenerate `configure' using a newer version of `autoconf'.
</del><ins>+ The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'. You only need
+`configure.ac' if you want to change it or regenerate `configure' using
+a newer version of `autoconf'.
</ins><span class="cx">
</span><span class="cx"> The simplest way to compile this package is:
</span><span class="cx">
</span><span class="lines">@@ -127,20 +70,22 @@
</span><span class="cx"> Compilers and Options
</span><span class="cx"> =====================
</span><span class="cx">
</span><del>- Some systems require unusual options for compilation or linking that
-the `configure' script does not know about. You can give `configure'
-initial values for variables by setting them in the environment. Using
-a Bourne-compatible shell, you can do that on the command line like
-this:
- CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
</del><ins>+Some systems require unusual options for compilation or linking that the
+`configure' script does not know about. Run `./configure --help' for
+details on some of the pertinent environment variables.
</ins><span class="cx">
</span><del>-Or on systems that have the `env' program, you can do it like this:
- env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
</del><ins>+ You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment. Here
+is an example:
</ins><span class="cx">
</span><ins>+ ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
+
+ *Note Defining Variables::, for more details.
+
</ins><span class="cx"> Compiling For Multiple Architectures
</span><span class="cx"> ====================================
</span><span class="cx">
</span><del>- You can compile the package for more than one kind of computer at the
</del><ins>+You can compile the package for more than one kind of computer at the
</ins><span class="cx"> same time, by placing the object files for each architecture in their
</span><span class="cx"> own directory. To do this, you must use a version of `make' that
</span><span class="cx"> supports the `VPATH' variable, such as GNU `make'. `cd' to the
</span><span class="lines">@@ -148,28 +93,28 @@
</span><span class="cx"> the `configure' script. `configure' automatically checks for the
</span><span class="cx"> source code in the directory that `configure' is in and in `..'.
</span><span class="cx">
</span><del>- If you have to use a `make' that does not supports the `VPATH'
-variable, you have to compile the package for one architecture at a time
-in the source code directory. After you have installed the package for
-one architecture, use `make distclean' before reconfiguring for another
-architecture.
</del><ins>+ If you have to use a `make' that does not support the `VPATH'
+variable, you have to compile the package for one architecture at a
+time in the source code directory. After you have installed the
+package for one architecture, use `make distclean' before reconfiguring
+for another architecture.
</ins><span class="cx">
</span><span class="cx"> Installation Names
</span><span class="cx"> ==================
</span><span class="cx">
</span><del>- By default, `make install' will install the package's files in
-`/usr/local/bin', `/usr/local/man', etc. You can specify an
-installation prefix other than `/usr/local' by giving `configure' the
-option `--prefix=PATH'.
</del><ins>+By default, `make install' installs the package's commands under
+`/usr/local/bin', include files under `/usr/local/include', etc. You
+can specify an installation prefix other than `/usr/local' by giving
+`configure' the option `--prefix=PREFIX'.
</ins><span class="cx">
</span><span class="cx"> You can specify separate installation prefixes for
</span><span class="cx"> architecture-specific files and architecture-independent files. If you
</span><del>-give `configure' the option `--exec-prefix=PATH', the package will use
-PATH as the prefix for installing programs and libraries.
-Documentation and other data files will still use the regular prefix.
</del><ins>+pass the option `--exec-prefix=PREFIX' to `configure', the package uses
+PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files still use the regular prefix.
</ins><span class="cx">
</span><span class="cx"> In addition, if you use an unusual directory layout you can give
</span><del>-options like `--bindir=PATH' to specify different values for particular
</del><ins>+options like `--bindir=DIR' to specify different values for particular
</ins><span class="cx"> kinds of files. Run `configure --help' for a list of the directories
</span><span class="cx"> you can set and what kinds of files go in them.
</span><span class="cx">
</span><span class="lines">@@ -180,7 +125,7 @@
</span><span class="cx"> Optional Features
</span><span class="cx"> =================
</span><span class="cx">
</span><del>- Some packages pay attention to `--enable-FEATURE' options to
</del><ins>+Some packages pay attention to `--enable-FEATURE' options to
</ins><span class="cx"> `configure', where FEATURE indicates an optional part of the package.
</span><span class="cx"> They may also pay attention to `--with-PACKAGE' options, where PACKAGE
</span><span class="cx"> is something like `gnu-as' or `x' (for the X Window System). The
</span><span class="lines">@@ -195,48 +140,86 @@
</span><span class="cx"> Specifying the System Type
</span><span class="cx"> ==========================
</span><span class="cx">
</span><del>- There may be some features `configure' can not figure out
-automatically, but needs to determine by the type of host the package
-will run on. Usually `configure' can figure that out, but if it prints
-a message saying it can not guess the host type, give it the
-`--host=TYPE' option. TYPE can either be a short name for the system
-type, such as `sun4', or a canonical name with three fields:
</del><ins>+There may be some features `configure' cannot figure out automatically,
+but needs to determine by the type of machine the package will run on.
+Usually, assuming the package is built to be run on the _same_
+architectures, `configure' can figure that out, but if it prints a
+message saying it cannot guess the machine type, give it the
+`--build=TYPE' option. TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+
</ins><span class="cx"> CPU-COMPANY-SYSTEM
</span><span class="cx">
</span><del>-See the file `config.sub' for the possible values of each field. If
</del><ins>+where SYSTEM can have one of these forms:
+
+ OS KERNEL-OS
+
+ See the file `config.sub' for the possible values of each field. If
</ins><span class="cx"> `config.sub' isn't included in this package, then this package doesn't
</span><del>-need to know the host type.
</del><ins>+need to know the machine type.
</ins><span class="cx">
</span><del>- If you are building compiler tools for cross-compiling, you can also
-use the `--target=TYPE' option to select the type of system they will
-produce code for and the `--build=TYPE' option to select the type of
-system on which you are compiling the package.
</del><ins>+ If you are _building_ compiler tools for cross-compiling, you should
+use the option `--target=TYPE' to select the type of system they will
+produce code for.
</ins><span class="cx">
</span><ins>+ If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+
</ins><span class="cx"> Sharing Defaults
</span><span class="cx"> ================
</span><span class="cx">
</span><del>- If you want to set default values for `configure' scripts to share,
-you can create a site shell script called `config.site' that gives
-default values for variables like `CC', `cache_file', and `prefix'.
</del><ins>+If you want to set default values for `configure' scripts to share, you
+can create a site shell script called `config.site' that gives default
+values for variables like `CC', `cache_file', and `prefix'.
</ins><span class="cx"> `configure' looks for `PREFIX/share/config.site' if it exists, then
</span><span class="cx"> `PREFIX/etc/config.site' if it exists. Or, you can set the
</span><span class="cx"> `CONFIG_SITE' environment variable to the location of the site script.
</span><span class="cx"> A warning: not all `configure' scripts look for a site script.
</span><span class="cx">
</span><del>-Operation Controls
</del><ins>+Defining Variables
</ins><span class="cx"> ==================
</span><span class="cx">
</span><del>- `configure' recognizes the following options to control how it
-operates.
</del><ins>+Variables not defined in a site shell script can be set in the
+environment passed to `configure'. However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost. In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'. For example:
</ins><span class="cx">
</span><del>-`--cache-file=FILE'
- Use and save the results of the tests in FILE instead of
- `./config.cache'. Set FILE to `/dev/null' to disable caching, for
- debugging `configure'.
</del><ins>+ ./configure CC=/usr/local2/bin/gcc
</ins><span class="cx">
</span><ins>+causes the specified `gcc' to be used as the C compiler (unless it is
+overridden in the site shell script). Here is a another example:
+
+ /bin/bash ./configure CONFIG_SHELL=/bin/bash
+
+Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
+configuration-related scripts to be executed by `/bin/bash'.
+
+`configure' Invocation
+======================
+
+`configure' recognizes the following options to control how it operates.
+
</ins><span class="cx"> `--help'
</span><ins>+`-h'
</ins><span class="cx"> Print a summary of the options to `configure', and exit.
</span><span class="cx">
</span><ins>+`--version'
+`-V'
+ Print the version of Autoconf used to generate the `configure'
+ script, and exit.
+
+`--cache-file=FILE'
+ Enable the cache: use and save the results of the tests in FILE,
+ traditionally `config.cache'. FILE defaults to `/dev/null' to
+ disable caching.
+
+`--config-cache'
+`-C'
+ Alias for `--cache-file=config.cache'.
+
</ins><span class="cx"> `--quiet'
</span><span class="cx"> `--silent'
</span><span class="cx"> `-q'
</span><span class="lines">@@ -248,8 +231,6 @@
</span><span class="cx"> Look for the package's source code in directory DIR. Usually
</span><span class="cx"> `configure' can determine that directory automatically.
</span><span class="cx">
</span><del>-`--version'
- Print the version of Autoconf used to generate the `configure'
- script, and exit.
</del><ins>+`configure' also accepts some other, not widely useful, options. Run
+`configure --help' for more details.
</ins><span class="cx">
</span><del>-`configure' also accepts some other, not widely useful, options.
</del></span></pre></div>
<a id="freeswitchtrunksrcswitch_corec"></a>
<div class="modfile"><h4>Modified: freeswitch/trunk/src/switch_core.c (15050 => 15051)</h4>
<pre class="diff"><span>
<span class="info">--- freeswitch/trunk/src/switch_core.c 2009-10-02 14:44:16 UTC (rev 15050)
+++ freeswitch/trunk/src/switch_core.c 2009-10-02 15:07:18 UTC (rev 15051)
</span><span class="lines">@@ -1346,13 +1346,6 @@
</span><span class="cx"> }
</span><span class="cx"> #endif
</span><span class="cx">
</span><del>-/* no ctl-c mofo */
-static void handle_SIGINT(int sig)
-{
- if (sig);
- return;
-}
-
</del><span class="cx"> static void handle_SIGHUP(int sig)
</span><span class="cx"> {
</span><span class="cx"> if (sig) {
</span><span class="lines">@@ -1463,7 +1456,7 @@
</span><span class="cx"> }
</span><span class="cx">
</span><span class="cx"> /* set signal handlers */
</span><del>- signal(SIGINT, handle_SIGINT);
</del><ins>+ signal(SIGINT, SIG_IGN);
</ins><span class="cx"> #ifdef SIGPIPE
</span><span class="cx"> signal(SIGPIPE, handle_SIGPIPE);
</span><span class="cx"> #endif
</span></span></pre>
</div>
</div>
<div id="footer">See you at ClueCon</div>
</body>
</html>