This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Keith keith at rhizomatica.orgOn 27/06/2019 21:55, ty wrote: > Hey all. Just bumping this since I haven’t heard any revert In fact there was a reply, via the mailing list, from Vasil who explained the last hurdles you were facing. http://lists.osmocom.org/pipermail/openbsc/2019-May/012932.html IIUC, you seem to have a goal which is to test/run an ip.access nanoBTS, however it seems you are getting bogged down in problems which are more leading you in the direction of C development, possibly distracting from your goal? My suggestions are: 1) If at all possible, build a new VM or install a fresh OS and install the osmo stack from packages. https://osmocom.org/projects/cellular-infrastructure/wiki/Latest_Builds If a fresh OS install is really not possible, then clean up your existing work machine; * run make uninstall for each component you installed from source. * Even then, check for and remove and libosmo* (and maybe other lib* and/or executables from osmo source) from where ever you installed from source. This is probably /usr/local/lib * Now install from packages. 2) Test your ip.access nanoBTS and deal with learning how to configure all the parts of the osmo stack to have it work. 3) If you want, and now with the first hand knowledge of what a running system looks like, return to the project of building from source. Be aware that there is a lot of development and things often move quickly. It does happen that you cannot clone one repo, and expect to compile it's master branch against libraries you compiled yesterday. If you are going to compile the entire stack, know that sometimes dependencies are not in obvious places. but for now, How do you feel about cleaning up your work machine and using the packages to get your hardware running?