Browse files

* Initial structure and import

git-svn-id: 0b225a68-5fa7-45c5-9c9e-d7f6881f360f
  • Loading branch information...
0 parents commit 4d9a43645b5d8db8dad099025bfcbd2a946e7fd1 amalysh committed Jun 14, 2010
Showing with 103,096 additions and 0 deletions.
  1. +3 −0 AUTHORS
  2. +2 −0 COPYING
  3. +7 −0 ChangeLog
  4. +236 −0 INSTALL
  5. +84 −0
  6. +711 −0
  7. +3 −0 NEWS
  8. +41 −0 README
  9. +30 −0 acinclude.m4
  10. +7,279 −0 aclocal.m4
  11. +23,376 −0 autom4te.cache/output.0
  12. +23,364 −0 autom4te.cache/output.1
  13. +355 −0 autom4te.cache/requests
  14. +9,458 −0 autom4te.cache/traces.0
  15. +642 −0 autom4te.cache/traces.1
  16. +1,411 −0 autotools/config.guess
  17. +1,500 −0 autotools/config.sub
  18. +530 −0 autotools/depcomp
  19. +323 −0 autotools/install-sh
  20. +6,911 −0 autotools/
  21. +360 −0 autotools/missing
  22. +66 −0 bootstrap
  23. +23,364 −0 configure
  24. +502 −0
  25. +44 −0 example/smppbox.conf.example
  26. +2 −0 example/smpplogins.txt.example
  27. +4 −0 gw/
  28. +468 −0 gw/
  29. +18 −0 gw/smppbox-cfg.def
  30. +1,683 −0 gw/smppbox.c
  31. +70 −0 rpm/
  32. +120 −0
  33. +60 −0 smppbox.log
  34. +69 −0 smppbox.patch
@@ -0,0 +1,3 @@
+Rene Kluwen <rene dot kluwen at chimit dot nl>
+Developers wanted to maintain package and documentation.
@@ -0,0 +1,2 @@
+See file KannelLICENSE for details about the license agreement for using,
+modifying, copying or deriving work from this software.
@@ -0,0 +1,7 @@
+ First repository release of smppbox standalone.
+ Some configuration options have been changed from the downloaded version:
+ - bearerbox-port added which replaces the smsbox-port in group = core
+ - bearerbox-host existed already but was not taken into account. It is now.
+ - global-sender removed (was not used)
@@ -0,0 +1,236 @@
+Installation Instructions
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
+Software Foundation, Inc.
+This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
+Basic Installation
+These are generic installation instructions.
+ The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation. It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions. Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+ 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.)
+ If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+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.
+ The file `' (or `') is used to create
+`configure' by a program called `autoconf'. You only need
+`' if you want to change it or regenerate `configure' using
+a newer version of `autoconf'.
+The simplest way to compile this package is:
+ 1. `cd' to the directory containing the package's source code and type
+ `./configure' to configure the package for your system. If you're
+ using `csh' on an old version of System V, you might need to type
+ `sh ./configure' instead to prevent `csh' from trying to execute
+ `configure' itself.
+ Running `configure' takes awhile. While running, it prints some
+ messages telling which features it is checking for.
+ 2. Type `make' to compile the package.
+ 3. Optionally, type `make check' to run any self-tests that come with
+ the package.
+ 4. Type `make install' to install the programs and any data files and
+ documentation.
+ 5. You can remove the program binaries and object files from the
+ source code directory by typing `make clean'. To also remove the
+ files that `configure' created (so you can compile the package for
+ a different kind of computer), type `make distclean'. There is
+ also a `make maintainer-clean' target, but that is intended mainly
+ for the package's developers. If you use it, you may have to get
+ all sorts of other programs in order to regenerate files that came
+ with the distribution.
+Compilers and Options
+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.
+ You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment. Here
+is an example:
+ ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
+ *Note Defining Variables::, for more details.
+Compiling For Multiple Architectures
+You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory. To do this, you must use a version of `make' that
+supports the `VPATH' variable, such as GNU `make'. `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script. `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.
+ 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.
+Installation Names
+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'.
+ You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files. If you
+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.
+ In addition, if you use an unusual directory layout you can give
+options like `--bindir=DIR' to specify different values for particular
+kinds of files. Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.
+ If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+Optional Features
+Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System). The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+ For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+Specifying the System Type
+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:
+where SYSTEM can have one of these forms:
+ See the file `config.sub' for the possible values of each field. If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+ 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.
+ 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'.
+Sharing Defaults
+If you want to set default values for `configure' scripts to share, you
+can create a site shell script called `' that gives default
+values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/' if it exists, then
+`PREFIX/etc/' if it exists. Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+Defining Variables
+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:
+ ./configure CC=/usr/local2/bin/gcc
+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.
+ Print a summary of the options to `configure', and exit.
+ Print the version of Autoconf used to generate the `configure'
+ script, and exit.
+ Enable the cache: use and save the results of the tests in FILE,
+ traditionally `config.cache'. FILE defaults to `/dev/null' to
+ disable caching.
+ Alias for `--cache-file=config.cache'.
+ Do not print messages saying which checks are being made. To
+ suppress all normal output, redirect it to `/dev/null' (any error
+ messages will still be shown).
+ Look for the package's source code in directory DIR. Usually
+ `configure' can determine that directory automatically.
+`configure' also accepts some other, not widely useful, options. Run
+`configure --help' for more details.
@@ -0,0 +1,84 @@
+man1pages = gw/smppbox.1
+man5pages = gw/smppbox.5
+docsrcs = $(wildcard grep -l '<!DOCTYPE ' doc/*.xml)
+docs = $(docsrcs:.xml=.html) $(docsrcs:.xml=.rtf) $( $(docsrcs:.xml=.pdf)
+rpmtemp = /tmp/smppbox-rpm
+pssrcs = $(wildcard doc/*.png)
+ps = $(
+figsrcs = $(wildcard doc/*.fig)
+figs = $(figsrcs:.fig=.png) $(
+ sed "s/#FIGTYPE#/.png/;s/#VERSION#/${VERSION}/;s/#DATE#/`date +%Y.%m.%d`/;s/#DRAFTS#/${DOCDRAFTS}/" $< > $*.tmp
+ ${JADE} -V nochunks -t sgml -d $(HTML_DSL) $*.tmp > $@
+ rm -f $*.tmp
+ sed "s/#FIGTYPE#/.ps/;s/#VERSION#/${VERSION}/;s/#DATE#/`date +%Y.%m.%d`/;s/#DRAFTS#/${DOCDRAFTS}/" $< > $*.tmp
+ cd `dirname $<` && $(JADE) -o `basename $*`.rtf -t rtf -d $(TEX_DSL) `basename $*`.tmp
+ rm -f $*.tmp
+ sed "s/#FIGTYPE#/.ps/;s/#VERSION#/${VERSION}/;s/#DATE#/`date +%Y.%m.%d`/;s/#DRAFTS#/${DOCDRAFTS}/" $< > $*.tmp
+ $(JADE) -o $*.tex -t tex -d $(TEX_DSL) $*.tmp
+ rm -f $*.tmp
+ cd `dirname $<` && $(JADETEX) `basename $*`.tex >/dev/null || true
+ cd `dirname $<` && $(JADETEX) `basename $*`.tex >/dev/null || true
+ cd `dirname $<` && $(JADETEX) `basename $*`.tex >/dev/null || \
+ ( echo Check `dirname $<`/`basename $*`.log for errors && false)
+ rm -f $*.log
+ cd `dirname $<` && $(DVIPS) -q -o `basename $*`.ps `basename $*`.dvi
+ rm -f $*.dvi $*.tex $*.aux
+ sed "s/#FIGTYPE#/.png/;s/#VERSION#/${VERSION}/;s/#DATE#/`date +%Y.%m.%d`/;s/#DRAFTS#/${DOCDRAFTS}/" $< > $*.tmp
+ $(JADE) -o $*.tex -t tex -d $(TEX_DSL) $*.tmp
+ rm -f $*.tmp
+ cd `dirname $<` && $(JADETEX) `basename $*`.tex >/dev/null || true
+ cd `dirname $<` && $(JADETEX) `basename $*`.tex >/dev/null || true
+ cd `dirname $<` && $(JADETEX) `basename $*`.tex >/dev/null || true
+ rm -f $*.log $*.dvi
+ cd `dirname $<` && $(PDFJADETEX) `basename $*`.tex > /dev/null || true
+ test -r $*.pdf || false
+ rm -f $*.log $*.tex $*.aux $*.out
+ $(FIG2DEV) -Lpng $< $@
+ $(FIG2DEV) -Lps $< $@
+ $(CONVERT) $< $@
+rpm: clean
+ @echo "Preparing to build the RPM files"
+ mkdir -p "$(rpmtemp)/${RPMPKG}"
+ cp -R * "$(rpmtemp)/${RPMPKG}"
+ tar -C "$(rpmtemp)" -c ${RPMPKG} -zf ${RPMPKG}.tar.gz
+ rm -rf "$(rpmtemp)/${RPMPKG}"
+ if [ -d $(rpmtemp) ]; then rmdir "$(rpmtemp)"; fi
+ @echo "Building the RPM"
+ rpmbuild -ta ${RPMPKG}.tar.gz
+ rm -f ${RPMPKG}.tar.gz
+ @echo "**********************************************************************"
+ @echo "* Success!"
+ @echo "* Your files are located under $(shell rpm --eval '%_rpmdir')"
+ @echo "* The Kannel Group <>"
+ @echo "**********************************************************************"
+ @echo "Thank you for using Kannel."
+docs: figs ps $(docs)
+figs: $(figs)
+ps: $(ps)
+pp: $(pres)
+EXTRA_DIST = KannelLICENSE bootstrap
Oops, something went wrong.

0 comments on commit 4d9a436

Please sign in to comment.