Re: dynamic versus statically linked libraries
> The phrasing we ended up using was...
There we go. That is what I was looking for. :-) Where is that written
in the specification, and if not then where do we insert it?
>: 5) If I have an LSB compliant application that dynamically or statically
>: links a non-LSB compliant library, then it is no longer LSB compliant
>: because of its dependency.
>I am guessing that you intend "a non-LSB compliant library" to mean "a
>library which is specified by LSB but does not comply with the
>specification", in which case [5] is probably correct.
My intent was to say a "non-LSB compliant library" meaning any library that
it is using APIs itself that are not specified by the LSB; therefore, as a
standalone program it is not LSB compliant. So, if an application cannot
call foo(), then a library cannot call foo() for the application with
respect to LSB compliance.
I appreciate your responses. This is clearing up my misunderstanding.
George (gk4)
Reply to: