In osmo-bts, we just have the configure flag --enable-sysmocom-bts, and don't pass a header include location. i.e. we expect the header files to exist locally.
I'm a bit stumped on why introducing stow would cause this to break. IIUC stow should only affect the installed dependencies, while the sysmocom headers are just placed in a local dir?
If we can't fix the osmo-bts build quickly, we'll have to revert the stow patch until that works.
https://jenkins.osmocom.org/jenkins/view/master/job/master-osmo-bts/36/BTS_M...
The build scripts are (obviously) in osmo-bts/contrib/ and osmo-ci/scripts.
Any help is appreciated.
~N
The incomplete fix for osmo-bts is available in https://gerrit.osmocom.org/#/c/5818/
The problem with headers location is fixed, the remaining issues are related to contrib/sysmobts-calib/ tool.
On Tue, Jan 16, 2018 at 02:20:13PM +0100, Max wrote:
The incomplete fix for osmo-bts is available in https://gerrit.osmocom.org/#/c/5818/
Excellent, didn't see that, thanks for taking this on. Posted some review...
~N
-
Max -
Neels Hofmeyr