From 521b83ba3a2844d1a4689aeae937ea0498e74f7c Mon Sep 17 00:00:00 2001 From: Oliver Smith Date: Wed, 30 Nov 2022 17:36:58 +0100 Subject: =?UTF-8?q?scripts/osmocom-build-old=E2=80=A6:=20skip=20openbsc=20?= =?UTF-8?q?1.4.{0,1}?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Don't attempt to build openbsc 1.4.0 and 1.4.1 in the osmocom-build-old-tags-against-master job, as it fails to build with a modern gcc with a potential null pointer dereference warning that gets treated as error. This was fixed in 1.4.2 with openbsc patch I93d816a20ba208e9fd32a1fc172a78ccd326e1ba. A more modern gcc gets used, as this job gets changed to not only run on jenkins nodes with debian 9 installed, but also more modern versions. This job does not run in docker, and since it still passes it doesn't seem worth changing that now. Related: OS#5793 Change-Id: Ibf4b66195fbd70a68d63929b156a9aac54a699bc --- scripts/osmocom-build-old-tags-against-master.sh | 2 ++ 1 file changed, 2 insertions(+) diff --git a/scripts/osmocom-build-old-tags-against-master.sh b/scripts/osmocom-build-old-tags-against-master.sh index 71d5a1f..b6e6138 100755 --- a/scripts/osmocom-build-old-tags-against-master.sh +++ b/scripts/osmocom-build-old-tags-against-master.sh @@ -54,6 +54,8 @@ tags_to_ignore() { echo "1.0.0" # testsuite echo "1.3.1" # testsuite: libosmocore 6407c822ae0d45d047deb0dff095f028a90c1ecc echo "1.3.2" # testsuite: libosmocore 6407c822ae0d45d047deb0dff095f028a90c1ecc + echo "1.4.0" # error: potential null pointer dereference, fixed in 1.4.2 + echo "1.4.1" # error: potential null pointer dereference, fixed in 1.4.2 ;; osmo-bsc) # Depends on libosmo-legacy-mgcp, but missing LIBOSMOLEGACYMGCP_CFLAGS so we can't build it with -- cgit v1.2.3