- Use $(INSTALL_DATA) for the header file.
- Make sure that also the libpri.so symlink gets installed.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
libosip2 already makes sure that the compiler emits position-independent
code. Adding $(FPIC) makes no difference. In addition the libosip2 build
system puts its own flag behind the CFLAGS, overriding whatever was set
before.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
- use $(INSTALL_BIN) and $(INSTALL_DATA) where possible.
- instead of creating symlinks manually just copy them.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
- Remove all flags/variables that are not used at all.
- dahdi-tools already makes sure that the compiler emits
position-independent code for libtonezone. Adding $(FPIC) makes no
difference. In addition the dahdi-toolsbuild system puts its own flag
behind the CFLAGS, overriding whatever was set before. Also the
applications should never be built with PIC, it should only be done for
the lib.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Remove all flags/variables that are not used at all. Remove some ':'
that are not needed in the context.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
bgg729 already makes sure that the compiler emits position-independent
code. Adding $(FPIC) makes no difference. In addition the bcg729 build
system puts its own flag behind the CFLAGS, overriding whatever was set
before.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Add TARGET_CPPFLAGS to TARGET_CFLAGS, otherwise OpenWrt's CPPFLAGS are
ignored (i.e. fortify-source headers are not picked up).
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Use the default Build/Compile. Use MAKE_VARS to set up the variables
that are used by pcapsipdump's Makefile.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
The include injects a lib depend on libuClibc++.so.0 into the package,
even on musl. Remove it and replace the depend with libstcpp instead.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Yate is the only package in OpenWrt which manually enables RTTI
(run-time type information). There's no explanation in the Makefile as
to why that would be needed or advisable. Remove it.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
With this include libuClibc++.so.0 gets added as a lib depend, even on
musl. readelf shows:
Dynamic section at offset 0x10ea60 contains 23 entries:
Tag Type Name/Value
0x0000000000000001 (NEEDED) Shared library: [libuClibc++.so.0]
0x0000000000000001 (NEEDED) Shared library: [libc.so]
0x0000000000000001 (NEEDED) Shared library: [libgcc_s.so.1]
0x000000000000000e (SONAME) Library soname: [libyate.so.6.0.0]
Remove the include from the Makefile and add a depend on libstdcpp
instead.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
This reverts commit 4cc2afdcdc which
disabled FORTIFY_SOURCE by removing OpenWrt's CPPFLAGS from the built.
Instead PKG_FORTIFY_SOURCE:=0 is defined, which is the proper way to do
it.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
rtpproxy doesn't use OpenWrt's CPPFLAGS (i.e. used for including
fortify-source headers). Add them to CFLAGS.
Run autoreconf. It's usually a good idea.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
- Version bump
- Refresh debug-disable patch
- Add patch to add missing includes to fix:
rtpp_record.c: In function 'rtpp_record_open':
rtpp_record.c:228:62: error: 'DEFFILEMODE' undeclared (first use in this function)
rrc->fd = open(rrc->spath, O_WRONLY | O_CREAT | O_TRUNC, DEFFILEMODE);
^
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Starting with 4.12 there are module build errors due to the
arch-specific uaccess.h using a macro defined in the generic include.
The generic include has been around since 2.6.18 and has always included
asm/uaccess.h, so switch to using the generic include for all kernels
which have it.
Example build failure:
CC [M] /data/bowl-builder/mips64_octeon/build/sdk/build_dir/target-mips64_octeon_64_musl/linux-octeon/dahdi-linux-2.11.1-20180111/drivers/dahdi/wcb4xxp/base.o
In file included from ../dahdi-linux-2.11.1-20180111/drivers/dahdi/wcb4xxp/base.c:38:0:
./arch/mips/include/asm/uaccess.h: In function 'eva_kernel_access':
./arch/mips/include/asm/uaccess.h:91:9: error: implicit declaration of function 'uaccess_kernel' [-Werror=implicit-function-declaration]
return uaccess_kernel();
^
cc1: some warnings being treated as errors
The same can currently be seen on arc_archs where also kernel 4.14.18 is
used.
The patch just follows what Ubuntu's Seth Forshee suggested for openafs,
which ran into the same problem. The commit message is largely just
copied from Seth's commit message as well :)
The issue has been reported to upstream here:
https://issues.asterisk.org/jira/browse/DAHLIN-360
The same patch has been uploaded there.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
- The libraries and the Berkeley DB recovery utility are currently in
Libraries/Telephony and Utilities/Telephony. That makes little sense
as the are not general purpose libraries/utilities, hence it is better
to move them to where Kamailio 5 sits in menuconfig.
- Rename them by adding prefixes "lib" and "util" to their name.
- Update their titles a bit.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
The recently added mod-db-berkeley comes with a companion utility.
Package kambdb_recover so it becomes available.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
This commit moves libkamailio-ims & libtrie into their own packages to
keep the main package small.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
kamailio comes with internal libraries. Some are not built when only the
standard group of modules is compiled (i.e. no modules selected in
menuconfig).
The problem is that there is no way to rely on specific internal
libraries being available in the main kamailio package.
To fix this this add some modules (if they are not already selected)
that will kick of the build of the internal libraries in any case.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
The INSTALL file from kamailio suggests to make the target "cfg" first.
All settinggs will then be reused when make is called again.
This has the side effect that "$(FPIC)" can be dropped from CFLAGS as
the build system adds the flags automatically now.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
When not specifying "run_target" the kamailio build system assumes
$(DESTDIR)/var/run/kamailio to be the run directory on the target
device. Add the variable to address this.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
The kamailio build system provides an RPATH "///usr/lib/kamailio/" when
linking. OpenWrt's rstrip.sh inspects this RPATH and drops it. Now the
modules cannot find the needed libraries. Fix this by specifying a path
that rstrip.sh accepts.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
The initial commit for this plugin missed that it comes with a
configuration file and extra files that go into
/usr/share/kamailio/xhttp_pi.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
This installs the snmp mibs files provided by mod_snmpstats. A patch is
added to make the kamailio build system install the files in a proper
location in PKG_INSTALL_DIR.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
The aim is to add the missing modules that Debian packages, minus the
ones for which depends are missing on OpenWrt.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
- add install/conffile routine
- use it for main package
- setup BuildKamailio5Module to allow inclusion of configuration files
on a per-module basis (mod-tls is currently the only user)
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
- dictionary.kamailio & kamailio-basic.cfg are gone, remove from
Makefilei accordingly
- Install the config files from PKG_INSTALL_DIR
- Use $(INSTALL_CONF) for config files
- Remove gratuitous directory creation
- Refresh 050-fix-kamailio-utils.patch
- Remove src/modules/cnxcc/Makefile change from 120-libevent-libs.patch
as $(EXTRA_LIBS) has been removed from Makefile in previous commit
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
