You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2023. It is now read-only.
I'll go ahead and answer this.
To simplify the answer for someone who may or may not understand the issue of shared library linking:
Linux is not Windows.
In Linux, in order for an application to work, it MUST have access to every part of the computer it wants to reach, the way it was originally written.
In a Linux application, there are numerous levels of abstraction (read: separation, and simplification, to ease the job of the programmer writing the application), and in many cases this is done through the use of "libraries".
These libraries then may reach backwards through libraries that they in turn are linked to...
In order for the entire system to work, these "dependencies" must match the environment in which they were programmed for.
OpenElec, ArkOS, TheRA, 351Elec, and CoreElec all have different base libraries, and even if they have the all of the correct libraries, there may be different versions....
To complicate things further, linux may require "firmware", that is software that runs on different components than the CPU itself, in order to ensure they speak the same API (dialect of the language they need to use to communicate with each other), and even these may be different, newer or older....
The stock RG351 firmware is the simplest hodge podge of garbage that someone could toss together to make it do the job that you bought the device for, generally by the lowest bidder, and certainly does not have all the dependencies required to run AnberPorts, or any of the software it delivers.
I hope this clears things up for you.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is there a specific reason why those ports are not working on stock rg351v firmware ?
The text was updated successfully, but these errors were encountered: