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_MODEL=sysmo,FIRMWARE_VERSION=master,a3=default,label=linux_amd64_debian8/console The build scripts are (obviously) in osmo-bts/contrib/ and osmo-ci/scripts. Any help is appreciated. ~N
signature.asc
Description: Digital signature
