Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - spina

Pages: [1]
YateBTS / Which c++ standard should we compile YateBTS with ?
« on: October 02, 2018, 05:30:18 PM »
As you might already know, YateBTS trunk does not compile with recent versions of GCC, due to a few errors related to iostream manipulations.

These errors are easy to fix in yate-bts source code (see

Though, I was confused why they were not an issue for you, I mean upstream. Which version of GCC do you use ? GCC 4.x, right ?

AFAIK, without otherwise specified:
By default, g++ is equivalent to g++ -std=gnu++14 since GCC 6, and g++ -std=gnu++98 for older releases.

And actually, if I set -std=gnu++98 in the appropriate Makefile, yate-bts compiles just fine.
My concern is that -std=gnu++98 and -std=gnu++14 may be somewhat different languages, and hence, depending on the C++ features and the GNU extensions the yate-bts source code actually use, and combine, building as -std=gnu++98 or -std=gnu++14 may not generate semantically identical object code.
Which makes me think that setting -std=gnu++98 might be a more consistent fix than (just) patching MSInfo.cpp and Sgsn.cpp to remove the compilation errors. Can someone confirm this ?

IMHO, if it's somewhat important to build the source code as 1998 ISO C++ with GNU extensions, it might be a good idea to enforce this through the Makefiles: -std=gnu++14 is the default for Ubuntu since Artful 17.10 (and thus for Bionic 18.04 LTS), for Debian since stretch, and obviously for Arch, which sum to a huge Linux users base. BTW, none of these users would be able to build YateBTS out of the box.   

The same question may also apply to C code (should we enforce -std=gnu99 or something else ?).
And may be also when building yate (server) itself: it compiles fine, but should we also enforce standards there ?

Thanks in advance for your answers.

  • I've attached the patches I use to consistently set -std=gnu++98 as C++ standard, and -std=gnu99 as C standard for both yate and yate-bts build files. I'm not sure it's the simplest/best fix, but yate and yate-bts build with GCC 8.2 without the need to otherwise patch the source code. 
    The diff are against versions 6.1.0-1, and may apply to any 6.x.
  • May be it still would not hurt to fix MSInfo.cpp and Sgsn.cpp, though ?

Kind regards,

YateBTS / Yate(BTS) instances as systemd services
« on: September 21, 2018, 03:48:26 PM »

I run Arch Linux, and got into troubles trying to manage Yate(BTS) instances using the sysv-init compatibility layer of systemd. Till recently this worked quite well using the init script provided with Yate source code (though lightly patched to always exit 0).
But its seems that newer (Arch) releases of systemd are not compiled anymore with the support to auto-generate unit service files from init scripts deployed to /etc/init.d. Which makes the provided one unhelpful.

I share bellow the simple tips I applied to get Yate(BTS) running as a systemd managed service.

First, create a unit file /etc/systemd/system/<unit-name>.service:
Code: [Select]
Description=<unit-name> or whatever

User=root or any user with appropriate permissions/capabilities


Code: [Select]



The file /etc/sysconfig/<unit-name> sets the environment variables used by the ybts-{start,stop} scripts, and would typically contain:

Once both files are written appropriately, run:
Code: [Select]
# systemctl daemon-reload to make systemd be aware of the new service, an then manage it using:
Code: [Select]
# systemctl {start,stop,status} <unit-name>.

IMHO, it's correct that the ybts-{start,stop} scripts always exit 0, as systemd will handle the dameon process life-cycle through its PID file, and not through the scripts exit value. Please correct me if I'm wrong.

There are other ways to achieve this, and more options available. But this might help getting started.
This pointer may also be worth reading if new to systemd:

Kind regards,

YateBTS / Building YateBTS on OS X
« on: September 19, 2018, 06:02:53 AM »
I would like to build and run YateBTS on OS X, basically because I can't achieve any kind of stability with my Linux laptop regarding USB3 transport and/or power management (neither bladerf nor Yate's fault, it's my hardware), and that I can put hands on an old MacBook Air.

It seems that Yate itself (the engine, message bus, main modules, SIP proxy, etc) should build/run fine, as I've seen that YateClient is available for OS X, and it does require Yate services to run.

My concern is the YateBTS part.
Let's try with the Linux source tree. AFAIK, its few requirements are tools and libraries I could install on OS X, including the full GNU toolchain, but:
- there may be Linux oddities in the Makefiles (about filesystem layout and/or file paths, environment variables, library names, whatever)
- source code may rely upon Linux specific (non POSIX) syscalls, that OS X will obviously not implement

Or should I try the the FreeBSD source tree, which is presumably closer to OS X ?
That would be far from my comfort zone, though, since I'm a true newbie when pushed to OS X / FreeBSD.

Has anyone already tried to build/run YateBTS on OS X ? Getting started with which source tree ?

Thanks in advance for any help or suggestion.

Kind regards,

YateBTS / yatebts 6.0.0 multuple compilation errors
« on: July 23, 2018, 07:00:10 AM »
Compiling latest yatebts releases (from SVN or tarball) fail with multiple errors related to c++ std streams manipulation.

For example:
MSInfo.cpp: In member function ‘bool GPRS::MSInfo::msAssignChannels()’:
MSInfo.cpp:641:86: error: no match for ‘operator<<’ (operand types are ‘std::ostream’ {aka ‘std::basic_ostream<char>’} and ‘std::ostringstream’ {aka ‘std::__cxx11::basic_ostringstream<char>’})
             GPRSLOG(INFO,GPRS_MSG|GPRS_CHECK_OK) << "Multislot assignment for "<<this<<os;
MSInfo.cpp:641:86: note: candidate: ‘operator<<(int, int)’ <built-in>
MSInfo.cpp:641:86: note:   no known conversion for argument 2 from ‘std::ostringstream’ {aka ‘std::__cxx11::basic_ostringstream<char>’} to ‘int’

AFAIK, this does not relate to invalid/missing dependencies, but rather to plain incorrect C++.

My build tool chain is:
Linux 4.17.6
GCC 8.1.1
libstdc++ 3.3.6

Thanks you for taking care of this issue.

Pages: [1]