Since recent system upgrade which pulled in sdcc 4.3.0, build fails with
following error:
/git/libusrp/firmware/include/fx2regs.h:324: syntax error: token -> '+' ; column 26
It seems newer sdcc doesn't like having sums directly in there. Using
parenthesis around the expression fixes the problem.
Related: OS#6157
Change-Id: Iccc0b1ffe95971957f16008c3e3b873d065ba0ea
With upgrading the debhelper compat level to v10, parallel building was
enabled by default. But this doesn't work reliably with libusrp, so
disable it. On OBS, out of 18 builds, two failed.
Related: OS#3970
Change-Id: Ic23778320a44ec6ee2fef499216eb8a0c52603d2
Change RESULT to ERROR so the configure script stops when SDCC is not
found. Otherwise it tries to use "no":
no -I../../firmware/include -c delay.c -o delay.rel
/bin/bash: line 1: no: command not found
Change-Id: Id8defcc72a35e469a1eeb59919d66cc7cf2f6ac8
Let's move to python3, it's 2020 and the conversion seemed
actually rather trivial (famous last words).
Change-Id: Ib1604b36c32630e1360e06567cbd5f63a78df547
Every time the get_proto_filename() is called, a new instance
of std::string is allocated for the first argument. When the
function returns, this instance gets deallocated. Therefore,
the returned user_filename.c_str() points to free()d memory.
Change-Id: Ib0007e9aebd9e77c28531c1ec70c61f1723a2d0d
Fixes: CID#240724
Generate the soname from LIBVERSION (initially 1:0:0), instead of VERSION.
This means, we have binary compatibility between each major release
(which we should increase if we ever have a breaking change), instead of
forcing a binary incompatibility for each packaged version (also nightly
packages). This is how we do it in other Osmocom projects, too.
Fix nightly RPM packaging, as we now don't need to add the git commit to
the package name:
[ 135s] libusrp.i586: E: shlib-policy-name-error (Badness: 10000) libusrp-3_4_4_4_c46f0
[ 135s] Your package contains a single shared library but is not named after its
[ 135s] SONAME.
The debian package is already using libusrp1 as package name.
Related: https://osmocom.org/projects/cellular-infrastructure/wiki/Make_a_new_release
Change-Id: I73b222ea7e2fd0117827f9d6f28b23671068533b
Remove OpenSUSE bug report link, set version to @VERSION@, make it build with
CentOS 8 etc.
Related: OS#4550
Change-Id: I453ff45ec449834dfee298ecc6015e6d54768bea
Without this patch, building on an RPI4 ends up with
BOOST_LDFLAGS=-L/usr/lib while libs are actually under
/usr/lib/arm-linux-gnueabihf, and configure will later file during
AX_BOOST_THREAD macro.
Change-Id: I7a6b2dca5ced6a6a5232fe78b071dfafdda0b0f3
Sometimes the jenkins job fails to build. I never have this issue
on my workstation. Disabling PARALLEL_MAKE is osmo-trx jenkins.sh (which
requires libusrp build) made libusrp stop failing there, so let's do the
same here.
OS#3970
Change-Id: Iab8eab6d21365e3ee8d018428a707c56cc1b72e5
Properly remove lk files to fix the following error during
"make distcheck".
ERROR: files left in build directory after distclean:
./firmware/src/usrp2/eeprom_boot.lk
./firmware/src/usrp2/std.lk
Change-Id: I5f1b1f5ad72112ba7212800da7f85846bb6e7187
Fix the script so it is python2 and python3 compatible, then let the
distro decide which python version to use.
Change-Id: If805c8167e2cf57ce3d6143dddfd4685ad729142
The script contains python2-only syntax, so it can only be run with
python2. Make sure to explicitly specify it needs to be run with python2
in order to run it fine on distros where python points to python3.
Change-Id: Ie695c26f1b2a4f84bdc2b67938fe37a4c50681dd
We recently re-introduced building the USRP1 FX2 firmware
using SDCC. This needs to be listed as requirement for building
the package, otherwise build are failing.
Change-Id: I23ca8d7ad26437f2c971608cd881a6f40e26a887
Back in df354005f3, for some reason
building the USRP1 FX2 firmware was disabled. Let's re-enable it, as
the FX2 firmware is required as an essential part of USRP1 device
operation. It's loaded into the FX2 RAM over USB after the initial USB
attach.
As the firmware code has meanwhile been ported to a more modern
SDCC dialect (SDCC 3.2 or later, released in 2012), we have to adjust
the required minimum SDCC version.
Change-Id: I66ecc66bca3e8c171d2dd0d15c71186e16e8cc3b
SDCC, at least from version 3 onwards, has change the names of special
attributes like "at" or "sfr". They are now all prefixed with double-
underscores.
Upstream fx2lib has made that change in commit 3071389d9a868ed553b84809b399008648536fcf
which can be obtained from
3071389d9a
Change-Id: I5df64bc3cc09402bdfacec9c256e96135e3688fd
When we forked libusrp from the gnuradio source archive, we moved
around the directories, but failed to adjust the FW_INCLUDES.
Change-Id: I51a10da2325f7f6d158bb80f43e42b6ed29006f0
The .tarball-version file should contain the *source version* uniquely
identifying the git commit, and not the Debian package name.
With https://gerrit.osmocom.org/#/c/osmo-ci/+/10343/ there is a correct
.tarball-version file in the .tar.xz of the nightly source packages.
Related: OS#3449
Change-Id: Idb187930d08b9e427ec07b4d27f138c106f69f99