Wanpipe Linux Setup Installation & RPMs
All wanpipe drivers support RPM building.
The ./Setup script is used to build RPMS. Depending on what drivers you need, you have to tell Setup to build rpms with certain protocols/drivers.
- Building RPMS from wanpipe sources
- Setup Usage
Building RPMS using Wanpipe Sources (Setup)
- Download latest wanpipe release
-> Location: wanpipe releases
- Untar wanpipe release in /usr/src directory
-> tar xfz wanpipe-<ver>.tgz
-> cd wanpipe-<ver>/
- Building RPMS
The ./Setup script is used to build RPMS.
Depending on what drivers you need, you have to tell Setup to build rpms with certain protocols/drivers.
Bulild RPMs for Asterisk/Zaptel: Modules and Utilities separately
-> ./Setup buildrpm --split_rpms --protocol=TDM --zaptel-path=/usr/src/zaptel
Building RPMs for Asterisk/Zaptel: One big rpm (modules + utilities)
-> ./Setup buildrpm --protocol=TDM --zaptel-path=/usr/src/zaptel
Building RPMs for WAN/Data/TDM API
Wan/Data/TDM API drives are installed by default so no extra options are needed
-> ./Setup buildrpm
or
-> ./Setup buildrpm --split_rpms
Bulding RPMs for WAN/Data/TDM API and Asterisk/Zaptel
-> ./Setup bulidrpm --protocol=DEF-TDM --zaptel-path=/usr/src/zaptel
or
-> ./Setup bulidrpm --split_rpms --protocol=DEF-TDM --zaptel-path=/usr/src/zaptel
The Setup script will prompt you with a summary of what its trying to do and what kernel it will build against. At this point you can choose to proceed or stop the build process.
Building RPMS non interactively
In some cases a non interactive build process is required. The ./Setup
script accepts the --silent flag that will default all options and
build the RPM without any questions.
-> ./Setup buildrpm --protocols=TDM --silent --zaptel-path=/usr/src/zaptel
Building RPMS (Non Interactive)
In some cases a non interactive build process is required. The ./Setup script accepts the --silent flag that will default all options and build the RPM without any questions.
-
-> ./Setup buildrpm --protocols=TDM --silent
Setup Installation Scrip Usage
./Setup {command} [ optinal command extensions ]
commands:
---------
install : Install/Upgrade WANPIPE
remove : Uninstall WANPIPE
utility : Re-compile WANPIPE Tools/Utilities
drivers : Re-install and Re-compile
WANPIPE kernel device drivers
buildrpm : Build the custom RPM binary for the
current system.
helprpm : RPM build help information.
<any key>: Help
optional command extensions:
----------------------------
--silent : Non interactive. Run all above commands
without user interaction. Thus default
environment values are assumed such
as:
Linux source dir: /lib/modules/2.6.9-16.ELsmp/build
Architecture : uname -m
Kernel Image : uname -r
--builddir : Install WANPIPE package into a virtual
directory. The path must be
absolute and must exist. Default is set
to system root( / ).
eg: --builddir=/root/wanpipe_build
--split_rpms: Option to split the rpm build into
util and modules package. Thus,
splitting user space utilities and
kernel modules into two packages.
Default: one rpm package containing
both utilites and modules.
eg: ./Setup buildrpm --split_rpms
--with-linux: Build modules using a custom linux
source directory. Default value is
set to /lib/modules/2.6.9-16.ELsmp/build
eg: --with-linux=/usr/src/linux-2.4.4
--arch : Build modules using a custom defined
architecture. (i686 or i586)
By default: (uname -m)
eg: --arch=i686
--linux-vanilla: Compile wanpipe drivers as if the
current linux source is a vanilla source.
Used to remove the default assumption that
stock distribution kernels pull changes
from higher linux kernel versions.
--no-gcc-debug: Remove -g option out of gcc compile argumetns.
--usr-cc :Use diffrent c compler then default $(CC)
--ocflags : Extra compile flags to append to CFLAGS during driver compilation
--kbuild-verbose : Enable linux 2.6. kernel build verbosity
--noautostart : Do not install boot start scripts to start wanpipe on boot
--zaptel-path : Source path to zaptel
--no-zaptel-compile: Do not compile zaptel during installation
Default mode is to compile zaptel source during install.
--gz-modules : Gzip the kernel modules when installing in /lib/modules directory
| 
