shared libraries should not be distributed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ffcall (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
As explained in http://
There is absolutely no reason to build libffcall shared libraries.
Moreover, they are actually harmful.
In fact, the crash reported in https:/
is caused by the shared libraries: when clisp is build with libffcall shared libraries (i.e., "-lavcall -lcallback")
the test suite segfaults, but when clisp is built with libffcall static libraries (i.e., "/usr/bin/
everything works just fine (as explained in
https:/
Let me repeat:
1. the package libffcall1 which only distributes libavcall.so and libcallback.so should be REMOVED.
There is no reason to distribute the shared libraries.
2. CLISP should be linked with libavcall.a and libcallback.a - statically.
otherwise it crashes in FFI callbacks.
3. libffcall1-dev should be kept, it works just fine; but it should NOT depend on libffcall1.
if you insist on using --enable-shared, you can just upgrade to the upstream cvs which now ignores --enable-shared