It seems the SDK (or some tools that merssh uses) are built against stretch CXX binarly api. This makes it unusuable on for example Debian 8.
Any chance this could get fixed?
| 2 | No.2 Revision |
It seems the SDK (or some tools that merssh uses) are built against debian stretch CXX (CXXABI_1.3.9) binarly api.
This makes it unusuable on for example Debian 8.8 (CXXABI_1.3.8).
Any chance this could get fixed?
| 3 | No.3 Revision |
It seems the SDK (or some tools that merssh uses) are built against debian stretch CXX (CXXABI_1.3.9) binarly api. This makes it unusuable on for example Debian 8 (CXXABI_1.3.8).
Any chance this could get fixed? fixed?
Or at least give support to debian 8 as well?
| 4 | No.4 Revision |
It seems the SDK (or some tools that merssh uses) are built against debian stretch CXX (CXXABI_1.3.9) binarly api. This makes it unusuable on for example Debian 8 (CXXABI_1.3.8).
Any chance this could get fixed? Or at least give support to debian 8 as well?
| 5 | No.5 Revision |
It seems the SDK (or some tools that merssh uses) are built against debian stretch CXX (CXXABI_1.3.9) binarly api. This makes it unusuable on for example Debian 8 (CXXABI_1.3.8).
Any chance this could get fixed? Or at least give support to debian 8 as well?
| 6 | No.6 Revision |
It seems the SDK (or some tools that merssh uses) are built against debian stretch CXX (CXXABI_1.3.9) binarly api. This makes it unusuable on for example Debian 8 (CXXABI_1.3.8).
Any chance this could get fixed? Or at least give support to debian 8 as well?
| 7 | No.7 Revision |
It seems the SDK (or some tools that merssh uses) are built against debian stretch stretch-level CXX (CXXABI_1.3.9) binarly api.
This makes it unusuable on for example Debian 8 (CXXABI_1.3.8).
Any chance this could get fixed? Or at least give support to debian 8 as well?
| 8 | No.8 Revision |
It seems the SDK (or some tools that merssh uses) are built against debian stretch-level CXX (CXXABI_1.3.9) binarly api.
binary interface.
This makes it unusuable on for example Debian 8 (CXXABI_1.3.8).
Any chance this could get fixed? Or at least give support to debian 8 as well?