We've seen the same in lynxis' debian builds of the split gits, and now it makes sense: The recent openggsn changes to debian rules somehow cause an oddity so that our configure check for libgtp now fails, causing all GPRS related binaries to not be built. Haven't investigated what exactly it is, but my expectation is that openggsn causes osmo-sgsn etc to fail:
My guess is https://git.osmocom.org/openggsn/commit/?id=23eea1d132120198745dcca32728906d... "Use osmocom-style git-version-gen / .version magic" (tagged 0.94)
We try to find it by: PKG_CHECK_MODULES(LIBGTP, libgtp >= 0.92, , found_libgtp=no)
log:
[ 60s] [110/216] installing libgtp1-0.93.20170812 [...] [ 61s] [116/216] installing libgtp-dev-0.93.20170812 [...] [ 138s] checking for LIBGTP... no
https://build.opensuse.org/public/build/network:osmocom:nightly/Debian_9.0/x...
~N
On Fri, Aug 11, 2017 at 08:04:10PM +0000, OBS Notification wrote:
Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/op...
Package network:osmocom:nightly/openbsc failed to build in Debian_9.0/x86_64
Check out the package for editing: osc checkout network:osmocom:nightly openbsc
Last lines of build log: [ 176s] make[4]: Leaving directory '/usr/src/packages/BUILD/openbsc/tests' [ 176s] make[3]: Leaving directory '/usr/src/packages/BUILD/openbsc/tests' [ 176s] make[3]: Entering directory '/usr/src/packages/BUILD/openbsc' [ 176s] make[4]: Entering directory '/usr/src/packages/BUILD/openbsc' [ 176s] make[4]: Nothing to be done for 'install-exec-am'. [ 176s] /bin/mkdir -p '/usr/src/packages/BUILD/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig' [ 176s] /usr/bin/install -c -m 644 openbsc.pc '/usr/src/packages/BUILD/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig' [ 176s] make[4]: Leaving directory '/usr/src/packages/BUILD/openbsc' [ 176s] make[3]: Leaving directory '/usr/src/packages/BUILD/openbsc' [ 176s] make[2]: Leaving directory '/usr/src/packages/BUILD/openbsc' [ 176s] make[1]: Leaving directory '/usr/src/packages/BUILD/openbsc' [ 176s] dh_install -O--sourcedirectory=openbsc [ 176s] dh_install: Cannot find (any matches for) "/usr/bin/osmo-sgsn" (tried in "." and "debian/tmp") [ 176s] dh_install: osmocom-sgsn missing files: /usr/bin/osmo-sgsn [ 176s] dh_install: Cannot find (any matches for) "/usr/bin/osmo-gtphub" (tried in "." and "debian/tmp") [ 176s] dh_install: osmo-gtphub missing files: /usr/bin/osmo-gtphub [ 176s] dh_install: missing files, aborting [ 176s] debian/rules:13: recipe for target 'binary' failed [ 176s] make: *** [binary] Error 2 [ 176s] dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 [ 176s] [ 176s] lamb17 failed "build openbsc_0.15.1.20170811.dsc" at Fri Aug 11 20:03:59 UTC 2017. [ 176s] [ 176s] ### VM INTERACTION START ### [ 180s] [ 168.503704] reboot: Power down [ 180s] ### VM INTERACTION END ### [ 180s] [ 180s] lamb17 failed "build openbsc_0.15.1.20170811.dsc" at Fri Aug 11 20:04:03 UTC 2017. [ 180s]
-- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/)
Hi Neels,
On Sun, Aug 13, 2017 at 03:00:32AM +0200, Neels Hofmeyr wrote:
My guess is https://git.osmocom.org/openggsn/commit/?id=23eea1d132120198745dcca32728906d... "Use osmocom-style git-version-gen / .version magic" (tagged 0.94)
sorry for the fall-out. I will investigate.
Hi Neels,
I've tried to reproduce this, unfortunately without success.
My steps were as follows:
* install a fresh Debian 9.0 VM image from "bento/debian-9.0" * install all build dependencies from official debian repository, namely: git build-essential autoconf libtool doxygen pkg-config libpcsclite-dev libtalloc-dev bumpversion autoconf-archive libdbi-dev libpcap-dev libssl-dev libc-ares-dev libortp-dev libsctp-dev libxml2-dev * for pkg in libosmocore libosmo-abis libosmo-netif libosmo-sccp libsmpp34 openggsn ** git clone ** dpkg-buildpackage ** dpkg -i resulting .deb
This gets me up to a point in having openggsn + all its dependencies installed
Then I proceed with git-clone + dpkg-buildpackage for openbsc.git, and it works just as expected. No errors. Specifically:
checking for LIBOSMOCORE... yes checking for LIBOSMOVTY... yes checking for LIBOSMOCTRL... yes checking for LIBOSMOGSM... yes checking for LIBOSMOABIS... yes checking for LIBOSMOGB... yes checking for LIBOSMONETIF... yes checking for LIBCRYPTO... yes checking for LIBOSMOSCCP... yes checking for LIBOSMOSCCP... yes checking for LIBSMPP34... yes checking for LIBGTP... yes checking for LIBCARES... yes
libgtp has: /usr/lib/x86_64-linux-gnu/pkgconfig/libgtp.pc and contains Version: 0.94.3-37d5
So I'm a bit at a loss what OBS-specific bits might be required, if it simply builds on a plain Debian 9.
On Sun, Aug 13, 2017 at 10:41:45AM +0200, Harald Welte wrote:
I've tried to reproduce this, unfortunately without success.
Update: After installing my own OBS instance + workers on local machines, I was able to reproduce this.
The culprit is libgtp.pc of those generated packages, which contains "Version: UNKNOWN" instead of the actual version. And the configure script of osmo-sgsn rightfully declines to recognize this as a supported version.
I'm not quite sure why it happens, and particularly why it only happens in OBS.
On Sun, Aug 13, 2017 at 07:15:39PM +0200, Harald Welte wrote:
I'm not quite sure why it happens, and particularly why it only happens in OBS.
In any case, I could fix it locally using https://gerrit.osmocom.org/#/c/3508/ which I just merged and now re-triggered the OBS nightly build (3 hours after its usual time).
-
Harald Welte -
Harald Welte -
Neels Hofmeyr