the ltesim_server is part of the UE package but needs to be executed
on the EPC run node. Therefore its handy to have the binary in the epc
trial tgz.
Change-Id: I21ac57d1c1547c1cf4d2394c8593f58ff2c78697
this allows to specify the environmental var
wanted_binaries_bin that will be included in the
trial package. if the variable isn't set, all three
main srsLTE binaries are included
Change-Id: I63f5799328435ce32b5bfd6dae6fd0b37e1e5397
Only newest OE SDKs have libmnl added, but we don't need this feature
anyway, so let's disable it in order to get builds running fine again.
Change-Id: Ief9cbca6e10b1ed6acf6e079f660fc3f7c863c7b
Only newest OE SDKs have libmnl added, but we don't need this feature
anyway, so let's disable it in order to get builds running fine again.
Change-Id: Id3b30d0b183cd21fd6df89fdda5581ab58c7a9a5
newer versions of srsLTE create symlinks with the rf library
including the version, see below. This caused the trx_zmq.so
lib to load .so.0 instead of .so only. this patch adds
another symlink so loading works fine again
libsrslte_rf.so -> libsrslte_rf.so.0
libsrslte_rf.so.0 -> libsrslte_rf.so.20.10.0
libsrslte_rf.so.20.10.0
Change-Id: Ib5302c9872f4c82a1ee5074f59de86709aa6c5a9
Nowadays we have instruction set runtime detection, so there's no point
in disabling it in the binary, specially because nowadays we run in sse
capable host (despite in the past we didn't and there was no runtime
detection, hence why was it explicitly disabled).
Change-Id: I2ffdc60c7644bb514a3854965d17109e91dda800
Some Amarisoft bundles may come without lteue in it. Allow the script to
run if that's the case by setting an envvar.
Change-Id: I363b44cd8aa48f80d24219b6bf5b3ebde580e3c3
It has been notified that current configuration system is difficult to
understand and to use, so it has been envisioned to refactor it a bit.
The idea is that the user passes a -c path/to/main.conf file, which in
turn contains whatever osmo-gsm-tester main settings supports (basically
what old paths.conf used to be, plus some files harcoded to the same -c
directory are now configurable through the main configuration file).
Change-Id: Ieca65b71b543c44cfcec8e83efd0fe053c432e55
Environment variable OSMO_GSM_TESTER_CONF is marked as deprecated and an
error is logged each time it's used. Same feature is available through
"-c" command line parameters, so having the envvar only makes things
more complex for no good reason. It cannot yet be completely dropped
since some environemnt still make use of it. Give some time to users to
adapt their setups.
Other environment variables setting some config apths can be dropped
since they are not being really used in any setup.
Change-Id: I7eb69f870d0dcb5906d45ae067d6bed1aabf5862
In the ENB case it's not really required since osmo-gsm-tester makes use
of LD_LIBRARY_PATH. However, since the UE is potentially run with
capabilitites to create tunnels and alike, LD_LIBRARY_PATH cannot be
used and lteue will fail to load trx_zmq.so (because it cannot find its
dependency libsrslte_rf.so).
Change-Id: Ifcbc6ed1c4c465b4cfab4c5689cde44624095f29
That module is only available so far in a private repository, so allow
still other amarisof tusers to build the bundles with UHD support.
Change-Id: I361f179c8e7f379173fa9109028e139fc4c8c251
During integration of the different srsLTE processes, some bugs or
misbehaviors appear which require fixes in srsLTE. Let's use our own
temporary fork until integration is complete and all patches are merged
in upstream.
Change-Id: I6414d9855cf9c004385cc280e5a60e82f8e4fbad
Since libosmo-abis d4be696bbc20522a0284b6d0aefa872585f6926f it is
enabled by default. Since we don't need it so far and required
dependencies are not available in sysmobts SDK, let's disable it
explicitly.
Change-Id: Id017f3d2f51d30fa53881b627460fb568f19713b
Some gcc version (< 7.3.0) on ARM generate wrong code for __thread
variables that crash at runtime. It seems, due to some unknown reason, that we
are not affected by this bug with toolchain from poky pyro (6.4.0). However,
libosmocore as of e188b8cd98f599468fbb200c7d590de955daf761 applies some
CFLAGS="-mtls-dialect=gnu2" to workaround the issue automatically. But same
toolchain contains an "ld" that crashes when those flags are applied.
Fortunately, libosmocore provides a way to disable the workaround, and since
we are not affected by the bug, we are fine with that. If the toolchain had
the TLS runtime bug, then we'd had to build with -O0. Can be probably dropped
once we move to newer toolchain.
Depends: libosmocore.git afce89dac1a3cdb975da72020acdba16940fd679
Related: OS#4062
Change-Id: I583354735a7671e5bba1c0f6e60c84b6ef55ac63
test -x for an empty string is still true. Check if the result of
command is empty or not. It seems to work for the negative case now.
Change-Id: I7e4326df155dae776481bf7824694b3fb47abcad
It's not common to run journald inside containers and the journalctl
command is not installed. Don't attempt to run it.
Change-Id: I9dee3cb0d0ca203da77dfa1a793a4e4e5f8593c6
Add contrib/jenkins-build-manuals.sh, which clones or updates
osmo-gsm-manuals and builds the manuals. When the environment variable
PUBLISH=1 is set, it also uploads them.
Call jenkins-build-manuals.sh from jenkins-run.sh, without PUBLISH=1,
so the manuals get build-tested in the osmo-gsm-tester_gerrit job.
A new job master-osmo-gsm-tester will be added in the future, which
will run PUBLISH=1 jenkins-build-manuals.sh.
The jenkins-build-manuals.sh script does not use the osmo-ci.git
scripts for installing dependencies and cleaning up the workspace.
These scripts are not available on the node, which runs the
osmo-gsm-tester_gerrit job, and it is not trivial to add just them
(without building the osmo-ci Docker image etc.). The only dependency
is osmo-gsm-manuals, and it does not need to be compiled, so it seemed
to be the most maintainable solution to implement the clone/update and
clean up in a few lines of shell code instead.
Related: OS#3385
Change-Id: I4ebfe12a164f807b63bc897aff44db83fc0705bd
Instead of each binary launcher having to check if there is a lib/
directory and then setting a LD_LIBRARY_PATH we can use an RPATH and
know these binaries pick-up the right libraries.
This requires I6e4ad2e3855af7bcefc22d4190cc4e6f58581857.
Change-Id: If771767dd82662e13b6b10ee7a8b8d0c84dcbdb1
Since osmo-sgsn f4b2c4ca42cc530c38c9ac6f275e4d7da9315fa2, it depends on
libosmo-gsup-client available in osmo-hlr.
Change-Id: I6aa997ff2092f9ddf2ac475fd094803be9063980
Inroduce a way to not take a 2x performance hit when testing. It
is of importance if we run with hundreds of BTSes and 10k+ subscribers.
In the absence of using getops or shflags use an environment for it.
Change-Id: I540ba1c35e8fb72abcee0d86e0bdc1136b47345c
Instead of cloning osmocom-bb three times this will allow us to
re-use the repository. Simply change the directory, set the new
origin and fetch.
Change-Id: I63f103b2f70559e969e8c66477ab9ee7f2886832
We want to write repo name in there, not $dep which actually doesn't
exist in local context of have_repo function. In most cases it's
actually the same because in almost all cases $dep is passed as $1 to
have_repo and thus is the same as local $repo. But in a few recipes
which don't use build_repo directly but instead use have_repo and build
manually, $dep may not point to $repo. That's the case for osmocom-bb
for instance. As a result, "libosmocore" is printed twice, were second
word should be "osmocom-bb".
Change-Id: I7a7db7cf4cc020295d216c60d6dc688f110916dc
To build osmo-nitb we need to clone "openbsc" and then enter the
"openbsc" sub-directory. For building "mobile" and "virt_phy" of
OsmocomBB we will need to do something similar. Instead of added
more hardcoded paths, add a variant that allows to specify the
source directory.
Change-Id: I67fbd54296f2c68316bf8e89cfeb37d147193d53