Osmo-PCU: make error

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Sipos Csaba sipos.csaba at kvk.uni-obuda.hu
Fri Dec 25 14:50:45 UTC 2015


Dear Jacob,

Today I started to update my setup to latest master for all the Osmocom projects and hit a compile error with Osmo-PCU:

root at D6420:~/newer_osmocom/osmo-pcu# make
Making all in src
make[1]: Entering directory `/root/newer_osmocom/osmo-pcu/src'
  CXX      gprs_debug.lo
  CXX      csn1.lo
  CXX      gsm_rlcmac.lo
  CXX      gprs_bssgp_pcu.lo
In file included from /usr/local/include/osmocom/gsm/prim.h:3:0,
                 from /usr/local/include/osmocom/gprs/gprs_bssgp.h:8,
                 from ./gprs_bssgp_pcu.h:32,
                 from gprs_bssgp_pcu.cpp:22:
/usr/local/include/osmocom/core/prim.h:23:27: error: uninitialized const 'osmo_prim_op_names' [-fpermissive]
 const struct value_string osmo_prim_op_names[5];
                           ^
In file included from /usr/local/include/osmocom/core/msgb.h:24:0,
                 from /usr/local/include/osmocom/gprs/gprs_ns.h:8,
                 from ./gprs_bssgp_pcu.h:31,
                 from gprs_bssgp_pcu.cpp:22:
/usr/local/include/osmocom/core/utils.h:22:8: note: 'const struct value_string' has no user-provided default constructor
 struct value_string {
        ^
/usr/local/include/osmocom/core/utils.h:23:15: note: and the implicitly-defined constructor does not initialize 'unsigned int value_string::value'
  unsigned int value; /*!< \brief numeric value */
               ^
make[1]: *** [gprs_bssgp_pcu.lo] Error 1
make[1]: Leaving directory `/root/newer_osmocom/osmo-pcu/src'
make: *** [all-recursive] Error 1

I can see that you moving some parts from openbsc to the core library, probably that process is not yet finsihed (or merged to master) and that is causing this problem.

Just wanted to give some feedback and notify the list about this.

Regards,
Csaba




More information about the OpenBSC mailing list