On Sat, May 12, 2018 at 11:35:51AM +0300, Nikos Balkanas wrote:
Dear Harald,
It was already pointed out to me, by Craig, that I was using the wrong list:( I was using this list, because osmocom-bb configure told me so, in each warning:(
Hmm, might be worth a patch.
Already have moved thread to baseband-devel. I arrived at this conclusion probably because git clone libosmocore (master branch), gives me libosmovty 0.9.0.16:( Will check out your link.
If you are building from source: the git tagged version is put in a file called .version. Sometimes I needed to remove that manually and start from scratch (autoreconf -fi; configure) to get a newer version. Maybe that helps?
~N
On Mon, May 14, 2018 at 2:29 PM, Neels Hofmeyr nhofmeyr@sysmocom.de wrote:
On Sat, May 12, 2018 at 11:35:51AM +0300, Nikos Balkanas wrote:
Dear Harald,
It was already pointed out to me, by Craig, that I was using the wrong list:( I was using this list, because osmocom-bb configure told me so, in each warning:(
Hmm, might be worth a patch.
I will be happy to submit one, if you tell me how to do it.
Already have moved thread to baseband-devel. I arrived at this conclusion probably because git clone libosmocore
(master
branch), gives me libosmovty 0.9.0.16:( Will check out your link.
If you are building from source: the git tagged version is put in a file called .version. Sometimes I needed to remove that manually and start from scratch (autoreconf -fi; configure) to get a newer version. Maybe that helps?
Hmmm. I don't think it is a versioning problem. The https request is ~6 mos old. The git request is upto date. Seems like caching from the nginx web server. Solved my problem by using the git request:)
~N
baseband-devel@lists.osmocom.org
-
Neels Hofmeyr -
Nikos Balkanas