It seems that 4 years ago in 2020 we merged Change-Id
Iab17f09380d7cd914cf85746b794c6c04ec7de43 to add MNCCv7 support, but
never actually tested mncc_sock.py ever since, as it still tries to
unconditionally access the 'ip' and 'port' members of the message,
which no longer exist due to the introduction of sockaddr_storage.
Working with sockaddr_storage is a bit nasty as it contains
double-underscores in the __ss_padding member, which means ctypes/python
will make it a private member that we cannot access. Work around this
with a small sed-script that removes the underscores from the
clang2py-generated python source code.
Change-Id: I3aa267a866ffaa54e7d71c19231adc78d3831169
This updates the mncc.h to V8 with GCR support, as introduced
in Change-ID I705c860e51637b4537cad65a330ecbaaca96dd5b of osmo-msc
Change-Id: Ia27956e42c6c2f494d59b89f42345462c86b10d2
After many years without ctypeslib maintenance, there's finally a
ctypeslib2 for python3.x
Instead of the crude gcc2xml hack it uses libclang to generate python
directly from the C.
Change-Id: I9efd56623ebeabef4317356a05484a620a3a91cc
This is a very crude port, including manual edits to the ctypeslib-generated
mncc.py file. There's no real clean way to do this, as ctypeslib is
ancient, abandoned and unmaintained.
Change-Id: Ie6ecd37353b35a6ac13c6578585c714c9ab46e06
Harald Welte
Pau Espin