See <https://jenkins.osmocom.org/jenkins/job/osmo-gsm-tester_build-osmocom-bb/47…>
Changes:
------------------------------------------
[...truncated 87.33 KB...]
Your branch is up to date with 'origin/master'.
+ rm -rf contrib doc include src
+ git reset --hard origin/master
HEAD is now at 621214c8 layer23: make all apps depend on libosmo-gprs-rlcmac
+ git rev-parse HEAD
621214c80297fee9a3279d4e94abdf2f92872b19
+ git rev-parse HEAD
+ echo 621214c80297fee9a3279d4e94abdf2f92872b19 osmocom-bb
+ cd <https://jenkins.osmocom.org/jenkins/job/osmo-gsm-tester_build-osmocom-bb/ws/>
+ cd osmocom-bb/src/host/osmocon
+ [ -f configure.ac ]
+ set +x
+ autoreconf -fi
configure.ac:13: installing './compile'
configure.ac:6: installing './install-sh'
configure.ac:6: installing './missing'
Makefile.am:10: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
Makefile.am:17: warning: source file '$(srcdir)/../../target/firmware/comm/sercomm.c' is in a subdirectory,
Makefile.am:17: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled. For now, the corresponding output
automake: object file(s) will be placed in the top-level directory. However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
Makefile.am: installing './depcomp'
+ set +x
+ ./configure --prefix=<https://jenkins.osmocom.org/jenkins/job/osmo-gsm-tester_build-osmocom-bb/ws…> --with-systemdsystemunitdir=no --enable-sanitize
configure: WARNING: unrecognized options: --with-systemdsystemunitdir
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking whether make sets $(MAKE)... (cached) yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... gcc3
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for LIBOSMOCORE... yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --with-systemdsystemunitdir
+ set +x
+ make -j8
echo 0.0.0.2844-6212 > .version-t && mv .version-t .version
make all-am
make[1]: Entering directory '<https://jenkins.osmocom.org/jenkins/job/osmo-gsm-tester_build-osmocom-bb/ws…'>
CC osmocon.o
CC tpu_debug.o
CC sercomm.o
CC osmoload.o
CCLD osmocon
osmoload.c: In function ‘loader_read_cb’:
osmoload.c:284:10: warning: ‘length’ may be used uninitialized in this function [-Wmaybe-uninitialized]
uint8_t length;
^~~~~~
osmoload.c:442:3: warning: ‘chip’ may be used uninitialized in this function [-Wmaybe-uninitialized]
loader_do_flashrange(cmd, msg, chip, address, status);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
osmoload.c:283:10: note: ‘chip’ was declared here
uint8_t chip;
^~~~
osmoload.c:442:3: warning: ‘status’ may be used uninitialized in this function [-Wmaybe-uninitialized]
loader_do_flashrange(cmd, msg, chip, address, status);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
osmoload.c:288:11: note: ‘status’ was declared here
uint32_t status;
^~~~~~
osmoload.c:429:5: warning: ‘crc’ may be used uninitialized in this function [-Wmaybe-uninitialized]
printf("\nbad crc %4.4x (not %4.4x) at offset 0x%8.8x", crc, osmoload.memcrc, osmoload.memoff);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
osmoload.c:285:11: note: ‘crc’ was declared here
uint16_t crc;
^~~
osmoload.c:410:4: warning: ‘data’ may be used uninitialized in this function [-Wmaybe-uninitialized]
loader_do_memdump(crc, data, length);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
osmoload.c:290:8: note: ‘data’ was declared here
void *data;
^~~~
osmoload.c:374:4: warning: ‘address’ may be used uninitialized in this function [-Wmaybe-uninitialized]
printf("Confirmed flash erase of chip %d address 0x%8.8x, status %s\n",
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
chip, address, status ? "FAILED" : "ok");
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
osmoload.c:286:11: note: ‘address’ was declared here
uint32_t address;
^~~~~~~
CCLD osmoload
make[1]: Leaving directory '<https://jenkins.osmocom.org/jenkins/job/osmo-gsm-tester_build-osmocom-bb/ws…'>
+ set +x
+ make install
make install-am
make[1]: Entering directory '<https://jenkins.osmocom.org/jenkins/job/osmo-gsm-tester_build-osmocom-bb/ws…'>
make[2]: Entering directory '<https://jenkins.osmocom.org/jenkins/job/osmo-gsm-tester_build-osmocom-bb/ws…'>
/bin/mkdir -p '<https://jenkins.osmocom.org/jenkins/job/osmo-gsm-tester_build-osmocom-bb/ws…'>
/usr/bin/install -c osmocon osmoload '<https://jenkins.osmocom.org/jenkins/job/osmo-gsm-tester_build-osmocom-bb/ws…'>
make[2]: Nothing to be done for 'install-data-am'.
make[2]: Leaving directory '<https://jenkins.osmocom.org/jenkins/job/osmo-gsm-tester_build-osmocom-bb/ws…'>
make[1]: Leaving directory '<https://jenkins.osmocom.org/jenkins/job/osmo-gsm-tester_build-osmocom-bb/ws…'>
+ build_repo_dir osmocom-bb src/host/layer23 --enable-sanitize
+ dep=osmocom-bb
+ dir=src/host/layer23
+ branch=master
+ echo --enable-sanitize
+ grep ^-
+ [ -z --enable-sanitize ]
+ shift
+ shift
+ configure_opts=--enable-sanitize
+ set +x
====================== osmocom-bb
+ have_repo osmocom-bb master
+ repo=osmocom-bb
+ branch=master
+ echo OSMO_GSM_TESTER_BUILD_osmocom-bb
+ sed s/-/_/g
+ branch_override_var=OSMO_GSM_TESTER_BUILD_osmocom_bb
+ eval echo $OSMO_GSM_TESTER_BUILD_osmocom_bb
+ echo
+ branch_override=
+ [ -n ]
+ cd <https://jenkins.osmocom.org/jenkins/job/osmo-gsm-tester_build-osmocom-bb/ws/>
+ [ -d osmocom-bb ]
+ cd osmocom-bb
+ git fetch
+ git rev-parse origin/master
621214c80297fee9a3279d4e94abdf2f92872b19
+ branch=origin/master
+ git checkout -B build_branch origin/master
Reset branch 'build_branch'
Branch 'build_branch' set up to track remote branch 'master' from 'origin'.
Your branch is up to date with 'origin/master'.
+ rm -rf contrib doc include src
+ git reset --hard origin/master
HEAD is now at 621214c8 layer23: make all apps depend on libosmo-gprs-rlcmac
+ git rev-parse HEAD
621214c80297fee9a3279d4e94abdf2f92872b19
+ git rev-parse HEAD
+ echo 621214c80297fee9a3279d4e94abdf2f92872b19 osmocom-bb
+ cd <https://jenkins.osmocom.org/jenkins/job/osmo-gsm-tester_build-osmocom-bb/ws/>
+ cd osmocom-bb/src/host/layer23
+ [ -f configure.ac ]
+ set +x
+ autoreconf -fi
configure.ac:10: installing './compile'
configure.ac:3: installing './install-sh'
configure.ac:3: installing './missing'
src/common/Makefile.am: installing './depcomp'
src/misc/Makefile.am:36: warning: source file '$(top_srcdir)/src/common/main.c' is in a subdirectory,
src/misc/Makefile.am:36: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled. For now, the corresponding output
automake: object file(s) will be placed in the top-level directory. However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
src/misc/Makefile.am:61: warning: source file '$(top_srcdir)/src/common/main.c' is in a subdirectory,
src/misc/Makefile.am:61: but option 'subdir-objects' is disabled
src/misc/Makefile.am:42: warning: source file '$(top_srcdir)/src/common/main.c' is in a subdirectory,
src/misc/Makefile.am:42: but option 'subdir-objects' is disabled
src/misc/Makefile.am:54: warning: source file '$(top_srcdir)/src/common/main.c' is in a subdirectory,
src/misc/Makefile.am:54: but option 'subdir-objects' is disabled
src/misc/Makefile.am:48: warning: source file '$(top_srcdir)/src/common/main.c' is in a subdirectory,
src/misc/Makefile.am:48: but option 'subdir-objects' is disabled
+ set +x
+ ./configure --prefix=<https://jenkins.osmocom.org/jenkins/job/osmo-gsm-tester_build-osmocom-bb/ws…> --with-systemdsystemunitdir=no --enable-sanitize
configure: WARNING: unrecognized options: --with-systemdsystemunitdir
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking whether make sets $(MAKE)... (cached) yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... gcc3
checking for ranlib... ranlib
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for LIBOSMOCORE... yes
checking for LIBOSMOVTY... yes
checking for LIBOSMOGSM... yes
checking for LIBOSMOCODEC... yes
checking for LIBOSMOGPRSRLCMAC... no
configure: error: Package requirements (libosmo-gprs-rlcmac) were not met:
Package 'libosmo-gprs-rlcmac', required by 'virtual:world', not found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables LIBOSMOGPRSRLCMAC_CFLAGS
and LIBOSMOGPRSRLCMAC_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
Build step 'Execute shell' marked build as failure
Skipped archiving because build is not successful