Project

General

Profile

Actions

Bug #5252

closed

eclipse-titan fails to build for Debian_Unstable on OBS

Added by osmith over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
10/11/2021
Due date:
% Done:

100%

Spec Reference:

Description

Apparently gcc has been upgraded in debian unstable, and now eclipse-titan fails to build:
https://build.opensuse.org/package/live_build_log/network:osmocom:latest/eclipse-titan/Debian_Unstable/x86_64

[  161s] g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -DYY_NO_INPUT -DNDEBUG  -DLINUX -DUSE_EPOLL -DYY_NO_INPUT -DNDEBUG  -DLINUX -DUSE_EPOLL -D_REENTRANT -g -O2 -ffile-prefix-map=/usr/src/packages/BUILD=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-long-long -O2 -fPIC -Wall -Wno-long-long -O2 -fPIC new.cc -o new.o
[  161s] new.cc:21:33: error: ISO C++17 does not allow dynamic exception specifications
[  161s]    21 | void *operator new(size_t size) throw (std::bad_alloc)
[  161s]       |                                 ^~~~~

We are building eclipse-titan 6.6.1, which was released in November 2019. The last version upstream tagged is 8.0.0 from June 2021.

The build failure has been fixed in newer releases:
https://gitlab.eclipse.org/eclipse/titan/titan.core/-/commit/05c39aa45cf1cc89f16c5566d87da9dc79ba838c

laforge: do you want me to upgrade to a new version (8.0.0?) or backport the patch?

Actions #1

Updated by laforge over 2 years ago

  • Status changed from Feedback to New
  • Assignee changed from laforge to osmith

I think there is no reason we should stay on ancient versions. Let's upgrade to latest upstream. In the past, the amount of fall-out was relatively minor during upgrades. Of course it makes sense to first at least test if osmo-ttcn3-tests at least still builds with 8.0.0.

Maybe fixeria knows, in the past he had been tracking upstream Titan relatively closely?

Actions #2

Updated by Hoernchen over 2 years ago

Just upgrade it, I don't think carrying compiler flag patches is worth the effort since we are bound to upgrade titan at some point anyway so we might as well just do it now, but just explicitly defaulting to c++14 or removing all the throws would also fix it.

Actions #3

Updated by osmith over 2 years ago

  • Status changed from New to In Progress
Actions #4

Updated by fixeria over 2 years ago

laforge wrote:

Maybe fixeria knows, in the past he had been tracking upstream Titan relatively closely?

I am currently using 7.2.2. Will give 8.0.0 a try and report back if I experience any issues.

Actions #5

Updated by osmith over 2 years ago

  • % Done changed from 0 to 50

This patch for regen-makefile.sh is needed: https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/25745

Otherwise "make compile" ran through (ttcn3 -> C++). I'm running "make all" right now (building all C++ sources).

As expected, 8.0.0 builds on debian unstable:
https://build.opensuse.org/package/show/home:osmith42:latest/eclipse-titan

Actions #6

Updated by osmith over 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100
With "make all", the following projects were slightly broken:
  • pgw
  • mme
  • selftest

We don't build these projects in jenkins, so they have probably been broken for some time.
Fixes submitted: https://gerrit.osmocom.org/q/topic:ttcn3-fix-make-all

Everything else built fine with 8.0.0 so I rolled it out to network:osmocom:latest:
https://build.opensuse.org/package/show/network:osmocom:latest/eclipse-titan

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)