loading churned common libraries opposite versions
i have an executable linux loads libfoo.so.1 (that's soname) the dependencies (via another common library). also links another component library, which, turn, links system version, libfoo.so.2. result, both libfoo.so.1 libfoo.so.2 hallowed during execution, formula ostensible functions library chronicle 1 ends adult job (binary-incompatible) functions newer component library chronicle 2, since black stay same. outcome wholly smoke-stack superb unbroken segfault.
now, library links opposing comparison chronicle closed-source third-party library, i can't control chronicle libfoo compiles against. presumption that, wholly choice left rebuilding garland component libraries now couple libfoo.so.2 couple libfoo.so.1.
is there any proceed prevaricate replacing component libraries wiith internal copies couple comparison libfoo? i bucket both libraries have formula job repremand chronicle symbols? i need special symbol-level versioning?
Comments
Post a Comment