laforge wrote in #note-1:
This is not a bug, reclassifying. It is the normal process of how building any software with GNU autotools works for the last 20+ years. the configure script checks your OS/environment for the availability of the (development) package of all its dependencies, and if they don't exist, it exits.
You will need to install libosmousb (part of libosmocore.git) first.
But honestly, if you are not familiar with building open source software with autotools, you really should use the binary packages. Please post the exact commands and output messages you're seeing for 'apt update' and 'apt install simtrace2-utils'. We do build the simtrace2 package and all of its dependencies every night for Ubuntu 22.04. My guess is that you somehow didn't install the proper apt configuration and/or key.
Proof of packages being built: https://obs.osmocom.org/package/binaries/osmocom:nightly/simtrace2/xUbuntu_22.04 - the results of which are at https://downloads.osmocom.org/packages/osmocom%3A/nightly/xUbuntu_22.04/amd64/
###################################################################################################################################################
Hi laforge,
Indeed you are right, i am not very familiar with building open source software, i only tried this way because binary packages were not working.
But you have just showed me why binary packages were not working.
The final command 'sudo apt-get install simtrace2-utils' in the documentation appears as 'sudo apt-get install simtrace2', hence, the package name would not be recognized, i just noticed now in your comments that we should add the -utils and everything is working now.
I was reading this page for tutorials
https://osmocom.org/projects/simtrace2/wiki
And on this page it says only simtrace2.
Thank you so much for your help, i will close this one as resolved.
Thanks,
Jelson G.