Similar fixes are applied in meta-telephony.git and
meta-sysmocom-bsp.git for recipes checking for existence of
netinet/sctp.h.
This is basically a poky pyro bug, already fixed in upstream poky
master (b11fc7795cd1a6d74c9bb50b922d928f4a17722d).
Change-Id: I330866badba8f30f500f74ac31e2c4e20b11d53c
Since osmo-bts.git a2dc808acc5b99122e97c9013cb1ec2ae0c4a2a1, osmo-bts
depends on libosmo-netif. Let's add the dependency when building.
Change-Id: I8e40b2de19ecfca084780f69808c7030817e43d7
Only newest OE SDKs have libmnl added, but we don't need this feature
anyway, so let's disable it in order to get builds running fine again.
Change-Id: Ief9cbca6e10b1ed6acf6e079f660fc3f7c863c7b
Since libosmo-abis d4be696bbc20522a0284b6d0aefa872585f6926f it is
enabled by default. Since we don't need it so far and required
dependencies are not available in sysmobts SDK, let's disable it
explicitly.
Change-Id: Id017f3d2f51d30fa53881b627460fb568f19713b
Some gcc version (< 7.3.0) on ARM generate wrong code for __thread
variables that crash at runtime. It seems, due to some unknown reason, that we
are not affected by this bug with toolchain from poky pyro (6.4.0). However,
libosmocore as of e188b8cd98f599468fbb200c7d590de955daf761 applies some
CFLAGS="-mtls-dialect=gnu2" to workaround the issue automatically. But same
toolchain contains an "ld" that crashes when those flags are applied.
Fortunately, libosmocore provides a way to disable the workaround, and since
we are not affected by the bug, we are fine with that. If the toolchain had
the TLS runtime bug, then we'd had to build with -O0. Can be probably dropped
once we move to newer toolchain.
Depends: libosmocore.git afce89dac1a3cdb975da72020acdba16940fd679
Related: OS#4062
Change-Id: I583354735a7671e5bba1c0f6e60c84b6ef55ac63
Pau Espin
Pau Espin Pedrol